rolldown
1.3.3 · 18 Nov 2026MIT181.7M / weekRepositoryHomepagenpmAtom feed
Upgrading rolldown From 0.3.0 to 1.3.3
57 releases in betweennotes for 48
Reading releases, release notes and advisories…
- 22+
- changes to make
- 0
- advisories fixed
- 227+
- new
- 298+
- fixes
Counted from 48 of 57 release notes, and the breaking changes of 7 pre-releases on the way to a major. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking1.3.2
- Breaking1.3.0
- Breaking1.2.10
- Breaking1.2.9
- Breaking1.2.3
- Breaking1.2.0
- Breaking0.10.0
- Breaking1.0.0-rc.1
- Breaking1.0.0-rc.2
- Breaking1.0.0-rc.2
Release by release
- New
Show plugin timings as a table
- New
Keep
g/dregex flags on the fast matcher - New
Free each module's AST as soon as it is printed
- New
Avoid per-chunk hash sets when hashing transitive chunk dependencies
- New
- Breaking
Drop no-op init calls from re-exports and imports
- New
magic-string: Add a
hiresconstructor option - New
cjs: Provide
__dirnameand__filenameto CommonJS modules in Node ESM output - New
Trace sequential sourcemap tokens with a bounded cursor
- Breaking
- New
inline-common-chunks: Inline chunks using
import.meta.ROLLDOWN_FILE_URL_* - New
Add the code location to transform logs and errors at position 0
- New
incremental: Reuse link-time facade symbols across rebuilds
- New
incremental: Share module sourcemap chains across cache clones
- New
- Breaking
Please read Breaking changes before upgrading.
- New
A page: LCP and FCP in a throttled browser (
scan). The build needs sourcemaps. - New
A Node.js or Deno server: the time until the server is ready (
node-scan). - New
A Cloudflare Worker: The time in global scope (
worker-scan).
- Breaking
- Fixed
Update @napi-rs/cli to 3.10.12 so linux-x64-gnu runs on older CPUs
- Fixed
- Fixed
sourcemap: Keep only traced sources and names in module sourcemaps (#11270)
- Fixed
- New
perf-kit: Check rendered output against the original build
- New
perf-kit: node/deno server startup mode
- New
perf-kit: Browser page-load perf harness for coding agents
- New
devtools: Report mode - agent-readable build metrics report
- New
- New
Mark module starts with
// <id>comments instead of#regionpairs - Fixed
Only register signal-exit handler when a trace subscriber is active
- New
14 other lines we could not sort, mostly version bumps
- 1.3.0
The same file imported with different attributes becomes different modules.
- 1.3.0
type: 'json','text'and'bytes'work without a plugin. - 1.3.0
Plugins can read the attributes in
resolveId,loadandtransform, and change them inresolveId. - 1.3.0
Packages: the largest packages, direct and transitive dependencies, and packages with more than one version.
- 1.2.11
"perf(dev/lazy): fetch a lazy route in one request"
- 1.1.5
"fix(hmr): fall back to full reload when a changed module is not registered as executed (#10132)"
- 1.1.4
"fix(plugin): make lazy hook metadata enumerable (#9991)"
- 1.1.2
Honor explicit non-TS extensions in
include(oxc-project/oxc-resolver#1213).compilerOptions.pathsnow resolve for importers whose extension is explicitly listed in a tsconfig'sinclude(e.g.src/**/*.vue,src/**/*.svelte). Previously oxc-resolver filtered importers by extension before evaluating theincludeglobs, so a.vue/.sveltefile listed inincludenever matched its project and itspathswere skipped. This unblocks the default create-vite Vue + TS layout (a solution-style root plus a referencedtsconfig.app.jsonthat declarespathsandinclude: ["src/**/*.ts", "src/**/*.vue"]). Matches vue-tsc and svelte-check, which register these extensions via TypeScript'sextraFileExtensions. - 1.1.2
No fallback to the outermost tsconfig in auto-discovery (oxc-project/oxc-resolver#1220). Auto-discovery no longer attaches the topmost ancestor
tsconfig.jsonto a file that no project actually owns (viafiles/include/ project references). Previously such a file inherited the outermost ancestor'spaths/baseUrl, leaking aliases into files that project does not own. oxc-resolver now returns no config in that case, matching tsserver / typescript-go, which route such files to an inferred project with no aliases. - 1.1.0
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.
778 internal lines (docs, tests, tooling) left out.
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.