@rolldown/debug
1.3.3 · 18 Nov 2026MIT312.2k / weekRepositoryHomepagenpmAtom feed
1.3.3 is the newest release of 1.x.
In short
7 new1 faster6 fixed3 changed22 internal
Release note
Important
This is a minor release. Two changes alter default behavior compared to 1.0.3. Please read this section before upgrading. Everything else is additive (new features, fixes, deps).
Notable behavior changes
1. experimental.lazyBarrel is now enabled by default (#9632)
What changed. experimental.lazyBarrel now defaults to true. When a barrel module is recognized as side-effect-free, Rolldown skips compiling the re-exported modules that are never actually used.
Impact. For codebases with large barrel files (component libraries such as Ant Design, @mui/icons-material, etc.) this is a meaningful build-time speedup, and for the vast majority of projects the emitted output is unchanged. In rare cases where a barrel is incorrectly treated as side-effect-free, the optimization could drop a module that was being relied on for its side effects.
How to opt out (backward compatible).
// rolldown.config.js
export default {
experimental: { lazyBarrel: false },
}Note: this opt-out flag is planned to be removed in a future release. If you have a case where you must turn it off, please open an issue so we can fix the underlying detection instead.
2. tsconfig project-reference resolution now aligns with TypeScript
Upgrading oxc_resolver (11.19.1 → 11.20.0 in #9549, then → 11.21.0 in #9634) changes how Rolldown discovers and resolves tsconfig.json, in particular for a solution-style config (one that only lists references and delegates the real settings to tsconfig.app.json / tsconfig.node.json, as Vite scaffolds), bringing it in line with how TypeScript (tsc / tsserver) itself behaves:
Auto-discovery walk-up (oxc-resolver #1154): in auto-discovery mode (
tsconfig: true, the default), Rolldown now searches upward from the file's directory and uses the firsttsconfig.jsonthat owns the file. Atsconfig.jsonowns the file when the file matches itsfiles/include/exclude, or when one of itsreferencesmatches the file. Atsconfig.jsonthat does not own the file is skipped, and the search continues in the parent directory. When notsconfig.jsonup the tree owns the file, Rolldown falls back to the outermost (topmost) one found, not the nearest. Previously the nearesttsconfig.jsonwas used unconditionally. This mirrors how TypeScript'stsserverassigns a file to a project.Reference match priority (oxc-resolver #1151): when the root has
references, a referenced project that includes the file now takes precedence over the root, instead of the root matching it first (this is what TypeScript already does). So that project'scompilerOptions.pathsnow apply.allowJs(oxc-resolver #1198): whether a.js/.jsx/.mjs/.cjsfile is included is now decided by each referenced project's ownallowJs, not the root's (again matching TypeScript). Sotsconfig.app.jsonwithallowJs: true+pathsnow resolves aliases for.jsfiles even when the root doesn't setallowJs.
For most projects this is a fix (the standard Vite paths aliases now resolve, closes rolldown/rolldown#8468), but it is a behavior change if you relied on the previous behavior, where the root's paths / allowJs took precedence.
If you relied on the old "root wins" behavior. There is no exact toggle back, because the old behavior was the bug being fixed. The recommended path is to align your config with TypeScript: declare the paths / allowJs on the referenced project that actually owns the files.
If you must keep the old precedence while still using references: a referenced project's match wins, and the first matching references entry takes priority (the root is only a fallback when no reference claims the file). So extract the old root settings into their own config and list it first:
// tsconfig.json (solution root)
{
"files": [],
"references": [
{ "path": "./tsconfig.base.json" }, // old root paths/allowJs — listed first, so it wins
{ "path": "./tsconfig.app.json" },
{ "path": "./tsconfig.node.json" }
]
}tsconfig.base.json should carry the paths you previously declared on the root, plus allowJs: true if it needs to claim .js files (the extension is checked against each config's own allowJs). With no include, it defaults to **/* under its directory and claims every file first.
One consequence of the new walk-up behavior to keep in mind: this solution root (files:, only references) has no file patterns of its own, so it owns a file only when one of its references matches it. When no tsconfig.json owns the file (for example a file outside tsconfig.base.json's directory), Rolldown does not fall back to this tsconfig.json. It keeps searching upward through ancestor directories. Before this release the nearest tsconfig.json was used unconditionally, so such files previously stopped at this solution root.
Alternatively, bypass reference resolution entirely by pointing the top-level tsconfig option at a single config: export default { tsconfig: './tsconfig.app.json' }.
Features
Enable
experimental.lazyBarrelby defaultimport.meta.globsupportcaseSensitiveoptionAdd
SOURCEMAP_BROKENwarning for renderChunk hookAdd
SOURCEMAP_BROKENwarning for transform hookAdd
@__NO_SIDE_EFFECTS__hint for invalid@__PURE__before function declarationscode-splitting: Support group-local
includeDependenciesRecursively
Bug Fixes
Report TSCONFIG_ERROR instead of UNHANDLEABLE_ERROR for a missing tsconfig file
browser: Add missing exports and ensure consistency with
rolldownpackageShould build test-dev-server when test-node
chunk-optimizer: Refuse asymmetric merge for cyclic dynamic entries
Handle slash-normalized ids with preserveModulesRoot
json: Preserve .default access on JSON default imports
testing: Remove unintended trigger_full_build from test harness
Performance
Avoid unnecessary intermediate sourcemaps
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.