rolldown
1.3.2 · 11 Nov 2026MIT164.1M / weekRepositoryHomepagenpmAtom feed
Where each line stands
Plan an upgrade- 1.x1.3.2No known advisoryLatest line
- 0.x0.15.1No known advisoryTo 1.3.2
Latest releases
All 66 releases1.3.2
11 Nov 2026- Removed
Drop no-op init calls from re-exports and imports
magic-string: Add a
hiresconstructor optioncjs: Provide
__dirnameand__filenameto CommonJS modules in Node ESM output
Features
magic-string: Add a
hiresconstructor optioncjs: Provide
__dirnameand__filenameto CommonJS modules in Node ESM output
Bug Fixes
strict-execution-order: Place re-export targets that no consumer selects
sourcemap: Use the
mapa hook returns with the native MagicString- Removed
Drop no-op init calls from re-exports and imports
Detect
__esModuleset withObject.defineProperty(module.exports, ...)Hoist
varin top-level catch blocks of wrapped modulesDetect top-level
awaitin top-levelcatchblockssourcemap: Keep columns when a hook returns the native MagicString
Make a module without module syntax CommonJS when it is both imported and required
Drop references in dead branches inside live functions before chunk linking
Make cross-chunk export names independent of module load order
Don't treat new URL() references as execution dependencies
Stop the options passed to hooks from keeping a build's plugins alive
strict-execution-order: Run the declaring module of an inlined constant read through a kept barrel
Hoist
varin top-level for-in and for-of heads of wrapped modulesrollup-tests: Fail the test case on assertion error in
renderErrorPreserve rendering errors when
renderErrorfailsCount emitted chunks when rendering relative-path externals
Avoid panic on
{ b: [y = 1] }destructuring in a wrapped moduletreeshaking: tree-shake statements with
instanceofthat a constant makes purerolldown: Fail the build instead of hanging when a module task panics
rolldown: Don't panic in module tasks after the build is dropped
browser: Default
cwdto/
Performance
Trace sequential sourcemap tokens with a bounded cursor
Use raw tokens when collapsing sourcemaps
magic-string: Free the index table of a MagicString returned from transform
1.3.1
9 Nov 2026inline-common-chunks: Inline chunks using
import.meta.ROLLDOWN_FILE_URL_*cli: Apply --environment before loading the binding
rolldown_plugin_vite_resolve: Escape module names in generated error stubs
Features
inline-common-chunks: Inline chunks using
import.meta.ROLLDOWN_FILE_URL_*
Bug Fixes
cli: Apply --environment before loading the binding
rolldown_plugin_vite_resolve: Escape module names in generated error stubs
Add the code location to transform logs and errors at position 0
Match sticky regexes only at the start of the string
iife/umd: Skip namespace markers when the entry has no exports
Keep a declaration's name when it clashes with an external import
Drop top-level statements made dead by imported constants before chunk linking
Keep
this.resolvecustom options apart for overlapping callstransform: Reuse TsconfigCache's answer when no tsconfig owns the file
Treat top-level
thisof a required module without module syntax as its exportsKeep side effects of a module whose exported constant is inlined
Leave same-chunk dynamic imports out of
dynamicImports
Performance
incremental: Reuse link-time facade symbols across rebuilds
incremental: Share module sourcemap chains across cache clones
chunk_optimizer: Answer runtime-merge reachability from one chunk-level graph
Send only changed chunk properties back to Rust from output hooks
1.3.0
5 Nov 2026The same file imported with different attributes becomes different modules.
type: 'json','text'and'bytes'work without a plugin.Plugins can read the attributes in
resolveId,loadandtransform, and change them inresolveId.
Important
This is a minor release. It adds experimental support for import attributes, and some changes alter default behavior compared to
1.2.16. Please read Breaking changes before upgrading.Warning
Vite users: Please do not force
rolldown@1.3.0into Vite withoverridesorresolutionsyet. Vite 8.3.6 and earlier need changes to work with it. Vite pins itsrolldownversion, so a normal install is not affected. Please wait for a Vite release that supports Rolldown 1.3.Import attributes support (experimental)
Import attributes are the
with { ... }part of an import. Node.js and browsers require them for JSON and CSS module scripts, so they are common in code written for these runtimes.import config from './config.json' with { type: 'json' }; import shader from './shader.glsl' with { type: 'text' }; import wasm from './module.wasm' with { type: 'bytes' };With
experimental.importAttributes:The same file imported with different attributes becomes different modules.
type: 'json','text'and'bytes'work without a plugin.Plugins can read the attributes in
resolveId,loadandtransform, and change them inresolveId.
// rolldown.config.js export default { experimental: { importAttributes: true, }, };The design follows Rollup 5. The option is off by default, because it changes the id of modules imported with attributes, and plugins that use the id as a file path can break.
Rolldown's dev mode and Vite do not support it yet. See the Import Attributes guide for details and plugin migration.
Agent-friendly build report (experimental)
With
devtools: { mode: 'report' }, Rolldown writes small Markdown and JSON files about each build tonode_modules/.rolldown/report/. A coding agent can read the numbers directly, and does not need scripts to parse a large event log. People and CI can use them too.// rolldown.config.js export default { devtools: { mode: 'report' }, };The report shows:
Packages: the largest packages, direct and transitive dependencies, and packages with more than one version.
See the Build Report guide for how to read each file and how to use the numbers in CI.
@rolldown/perf-kit(experimental)@rolldown/perf-kitis a new package that consumes the data fromdevtools: { mode: 'report' }and adds its own measurements. An agent or a person can use the processed data to improve LCP, FCP and startup time. A fixed baseline and a check of the rendered output show which changes to keep.npx @rolldown/perf-kit help
It measures 3 targets:
A page: LCP and FCP in a throttled browser (
scan). The build needs sourcemaps.A Node.js or Deno server: the time until the server is ready (
node-scan).A Cloudflare Worker: The time in global scope (
worker-scan).
See the Perf Kit guide for the agent prompts and more details.
We compared an agent alone with an agent using perf-kit on 3 open-source Cloudflare Workers. The prompts, results and steps to reproduce are in perf-kit-worker-startup.
Breaking changes
preserveModulesfile names now follow Rollup (#11410, #11413)[name]now keeps non-JS extensions, sodata.jsonbecomesdata.json.jsinstead ofdata.js, andComp.vuebecomesComp.vue.jsinstead ofComp.js. Libraries that pointexportsat the old file names need to update them.CLI:
--inputcannot be used together with positional entries (#11445)rolldown 1.js --input 2.jsnow fails. Userolldown 1.js 2.jsorrolldown --input 1.js --input 2.js.Notable fixes
External imports keep their attributes correctly (#11302, #11303)
This applies to every build, with or without
experimental.importAttributes. Before, two imports of one external with different attributes became one module, and one import was lost. The legacyassertkeyword was also copied to the output, which Node.js 22+ cannot load.// input (`ext` is external) import 'ext'; import 'ext' with { type: 'json' }; import data from 'ext2' assert { type: 'json' }; // 1.2.16 output import 'ext' with { type: 'json' }; import data from 'ext2' assert { type: 'json' }; // 1.3.0 output, with a DEPRECATED_IMPORT_ASSERTION warning import 'ext'; import 'ext' with { type: 'json' }; import data from 'ext2' with { type: 'json' };Plugins now see such an external with the attributes in its id, for example
ext?attributes=%7B%22type%22%3A%22json%22%7Dinthis.getModuleIds().Features
Expose notify APIs
Bug Fixes
Respect
NO_COLORin error and warning diagnosticsAvoid following output directory symlinks with
output.cleanDirEscape URL in sourceMappingURL
Error when one module id resolves as both external and non-external
Give module namespace objects a
nullprototype and make them non-extensibleDerive reference ids from stable seeds for deterministic builds
Avoid inferring constants from compound CommonJS exports
Don't inline a CommonJS export that is assigned conditionally or also through
module.exportsRespect
externalLiveBindingsfor star re-exports from externals in cjsDon't export JSON keys that the finalizer inlines away from a shared chunk
Handle nullish thrown values in error summary
Don't inline a
varthat module-level code reads before its declarationTreat a repeated
vardeclaration as a reassignment
Dependency tracking · free for 3 projects
Know when your own dependencies move
rolldown shipped a new major in the last 12 months, among 37 releases. inlinr shows which of your projects are behind, and what the upgrade breaks.
Advisories reach you
An email when a critical or high advisory affects a project, before the next install.
Upgrades checked first
Peer ranges, Node, ESM-only and types changes read before you bump.
Only what matters
Majors and breaking notes stay; patches and sibling bumps fold into one line.
Reading releases, release notes and advisories…
Registry facts last checked 11 Nov 2026. Releases and advisories last read 11 Nov 2026.