Packages

rolldown

1.3.3 · 18 Nov 2026MIT181.7M / weekRepositoryHomepagenpmAtom feed

Upgrading rolldown From 0.11.0 to 1.3.3

48 releases in betweennotes for 43

Reading releases, release notes and advisories…

Other targets from 0.11.0Newest 0.x0.15.1
  1. 0.11.0yours
  2. 1 release
  3. 0.12.0major
  4. 2 releases
  5. 0.13.0major
  6. 2 releases
  7. 0.14.0major
  8. 0.15.0major
  9. 1 release
  10. 1.0.0major
  11. 36 releases
  12. 1.3.3target
  13. 30 pre
21+
changes to make
0
advisories fixed
217+
new
298+
fixes

Counted from 43 of 48 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
  • Breaking1.0.0-rc.1
  • Breaking1.0.0-rc.2
  • Breaking1.0.0-rc.2
  • Breaking1.0.0-rc.2

Release by release

  1. 1.3.3

    18 Nov 20268 new · 18 fixes
    • New

      Show plugin timings as a table

    • New

      Keep g/d regex 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

  2. 1.3.2

    Migration needed11 Nov 20265 new · 21 fixes
    • Breaking

      Drop no-op init calls from re-exports and imports

    • New

      magic-string: Add a hires constructor option

    • New

      cjs: Provide __dirname and __filename to CommonJS modules in Node ESM output

    • New

      Trace sequential sourcemap tokens with a bounded cursor

  3. 1.3.1

    9 Nov 20266 new · 11 fixes
    • 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

  4. 1.3.0

    Migration needed5 Nov 20264 new · 13 fixes
    • 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).

  5. 1.2.19

    11 Nov 20261 fix
    • Fixed

      Update @napi-rs/cli to 3.10.12 so linux-x64-gnu runs on older CPUs

  6. 1.2.18

    9 Nov 20261 fix
    • Fixed

      sourcemap: Keep only traced sources and names in module sourcemaps (#11270)

  7. 1.2.16

    29 Oct 202613 new · 17 fixes
    • 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

  8. 1.2.15

    21 Oct 20261 new · 1 fix
    • New

      Mark module starts with // <id> comments instead of #region pairs

    • Fixed

      Only register signal-exit handler when a trace subscriber is active

14 other lines we could not sort, mostly version bumps
  • 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, load and transform, and change them in resolveId.

    1.3.0
  • Packages: the largest packages, direct and transitive dependencies, and packages with more than one version.

    1.3.0
  • "perf(dev/lazy): fetch a lazy route in one request"

    1.2.11
  • "fix(hmr): fall back to full reload when a changed module is not registered as executed (#10132)"

    1.1.5
  • "fix(plugin): make lazy hook metadata enumerable (#9991)"

    1.1.4
  • Honor explicit non-TS extensions in include (oxc-project/oxc-resolver#1213). compilerOptions.paths now resolve for importers whose extension is explicitly listed in a tsconfig's include (e.g. src/**/*.vue, src/**/*.svelte). Previously oxc-resolver filtered importers by extension before evaluating the include globs, so a .vue/.svelte file listed in include never matched its project and its paths were skipped. This unblocks the default create-vite Vue + TS layout (a solution-style root plus a referenced tsconfig.app.json that declares paths and include: ["src/**/*.ts", "src/**/*.vue"]). Matches vue-tsc and svelte-check, which register these extensions via TypeScript's extraFileExtensions.

    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.json to a file that no project actually owns (via files / include / project references). Previously such a file inherited the outermost ancestor's paths / 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.2
  • 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 first tsconfig.json that owns the file. A tsconfig.json owns the file when the file matches its files/include/exclude, or when one of its references matches the file. A tsconfig.json that does not own the file is skipped, and the search continues in the parent directory. When no tsconfig.json up the tree owns the file, Rolldown falls back to the outermost (topmost) one found, not the nearest. Previously the nearest tsconfig.json was used unconditionally. This mirrors how TypeScript's tsserver assigns a file to a project.

    1.1.0

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.