web-infra-dev
rspack
Blog
Docs
Changelog
Blog
Docs
Changelog
Overview
Branches
Benchmarks
Runs
Performance History
Latest Results
test(cache): cover context dependency timestamps
codex/snapshot-context-module-canary
7 minutes ago
fix(mf): stabilize consume shared runtime output
2heal1:fix/issue-4830-deterministic-consumes
16 minutes ago
test(hash): update hash snapshots
codex/rspack_content_hash
24 minutes ago
fix(mf): stabilize consume shared runtime output
2heal1:fix/issue-4830-deterministic-consumes
46 minutes ago
fix(css): expose exportType runtime helpers
codex/export-type-css
54 minutes ago
fix(css): preserve undeclared css module idents (#14497) * fix(css): preserve undeclared css module idents * fix(css): include icss custom property declarations * test(css): move issue 14495 regression case * test(css): format issue 14495 config
main
55 minutes ago
fix: preserve createRequire().resolve with literal import.meta.url when requireResolve is disabled When `module.parser.javascript.requireResolve` is `false`, a created require's `.resolve(...)` is preserved to run at runtime instead of being rewritten to a module id. A created require used for `.resolve` is rendered via rspack's injected `__rspack_createRequire` helper, so the literal `import.meta.url` resolves relative to the runtime output module (like a normal preserved `require.resolve`) rather than a build-time source path. A created require used only for plain `require(...)` (never `.resolve`) is cleared to `undefined`, so a dead `import.meta.url` never leaks into the artifact and CommonJS output stays valid. The clear/keep decision is deferred to `finish()`, driven by whether a `.resolve` use is seen. Since literal `import.meta.url` is only valid in ESM output, an `Unsupported feature` warning is emitted when a preserved `createRequire(import.meta.url)` would land in a CommonJS bundle.
fy/clever-sammet-433c80
56 minutes ago
revert: drop shadowed cjs exports handling from parse plugin The is_free guards in CommonJsExportsParserPlugin treated shadowed / require-tagged `exports`/`module` locals as non-exports. That is a pre-existing CJS codegen concern, out of scope for the side-effects change; revert the parse plugin to base and defer it to the unified CJS fix. The side-effects `is_common_js_export_assignment` is_free guard (which keeps shadowed-setter modules from being over-tree-shaken) is unchanged. Drops the tagged-shadowed-* fixtures that asserted the removed behavior.
fy/cjs-export-assignment-side-effects
1 hour ago
Latest Branches
CodSpeed Performance Gauge
-1%
refactor: split content hash from std Hash
#14384
38 minutes ago
c66f126
codex/rspack_content_hash
CodSpeed Performance Gauge
0%
fix(mf): stabilize consume shared runtime output
#14532
1 hour ago
4d14d7d
2heal1:fix/issue-4830-deterministic-consumes
CodSpeed Performance Gauge
0%
feat(css): support parser exportType
#14095
2 hours ago
2da0daa
codex/export-type-css
© 2026 CodSpeed Technology
Home
Terms
Privacy
Docs