rollup-plugin-chunk-per-export
v1.0.2
Published
Rollup plugin that ensures different exports are in different files for optimal tree-shaking
Downloads
156
Readme
rollup-plugin-chunk-per-export
This plugin analyzes your Rollup bundle, and ensures each export ends up in a separate file (a "chunk", in Rollup parlance). Any dependencies called from each of those exports, are still bundled normally and shared between chunks if needed.
Why
Tree-shaking. If you're making a library that's going to end up in somebody's browser, you want to make sure that bundlers can tree-shake your library, and takes only the parts of your library that are being used.
However, bundlers do often play it safe and only tree-shake along file boundaries. That is, if you use smallFunction
, but it's in the same file as bigFunction
, both of them will end up in the final bundle, just in case you do call that function somehow. In my experience this is true even if you set "sideEffects": false
in your package.json
.
It is unfortunate then, that Rollup (as bundlers do), likes to put all of your code in the same file, if you're creating a library. That's where this plugin comes in.
Comparison
Before
flowchart LR
style Input fill:transparent
style Output fill:transparent
subgraph Input
subgraph in-helpers [helpers.js]
direction TB
in-helper-foo[export const helper1]
in-helper-bar[export const helper2]
in-helper-none[export const helper3]
end
subgraph in-bar [bar.js]
direction TB
in-bar1[export const bar1]
--> in-helper-bar
in-bar2[export const bar2]
--> in-helper-none
end
subgraph in-foo [foo.js]
direction TB
in-foo1[export const foo1]
--> in-helper-foo
in-foo2[export const foo2]
--> in-helper-bar
end
subgraph in-main [main.js]
direction TB
in-import-all[export * from './foo.js']
--> in-foo1 & in-foo2
in-import-named["export { bar1 } from './bar.js'"]
--> in-bar1
end
end
subgraph Output
subgraph out-main [main.js]
direction TB
out-helper-bar[export const helper2]
out-bar1[export const bar1]
--> out-helper-bar
out-foo1[export const foo1]
--> out-helper-foo[const helper1]
out-foo2[export const foo2]
--> out-helper-bar
end
end
Input --Rollup--> Output
After
flowchart LR
style Input fill:transparent
style Output fill:transparent
subgraph Input
subgraph in-helpers [helpers.js]
direction TB
in-helper-foo[export const helper1]
in-helper-bar[export const helper2]
in-helper-none[export const helper3]
end
subgraph in-bar [bar.js]
direction TB
in-bar1[export const bar1]
--> in-helper-bar
in-bar2[export const bar2]
--> in-helper-none
end
subgraph in-foo [foo.js]
direction TB
in-foo1[export const foo1]
--> in-helper-foo
in-foo2[export const foo2]
--> in-helper-bar
end
subgraph in-main [main.js]
direction TB
in-import-all[export * from './foo.js']
--> in-foo1 & in-foo2
in-import-named["export { bar1 } from './bar.js'"]
--> in-bar1
end
end
subgraph Output
subgraph out-helpers [chunk-e8b73.js]
direction TB
out-helper-bar[export const helper2]
end
subgraph out-bar [chunk-50dd2.js]
direction TB
out-bar1[export const bar1]
--> out-helper-bar
end
subgraph out-foo [chunk-cc3d6.js]
direction TB
out-foo1[export const foo1]
--> out-helper-foo[const helper1]
out-foo2[export const foo2]
--> out-helper-bar
end
subgraph out-main [main.js]
direction TB
out-import-all["export { foo1, foo2 } from './chunk-cc3d6.js'"]
--> out-foo1 & out-foo2
out-import-named["export { bar1 } from './chunk-50dd2.js'"]
--> out-bar1
end
end
Input --Rollup--> Output
Without this plugin, Rollup bundles everything into the same file. With the plugin, each export from main.js
is forced to be on their own file.
It does look more complex when the plugin is added, but remember that bundlers usually only tree-shake along file boundaries (yellow background); so it is more able to pick-and-choose specific exports.
Limitations
Your authored code should already be split into multiple files. This plugin does not move exports into their own file.
Therefore, exports defined in the same file in your authored code, will also end up in the same file in the build output.
It follows re-exports, but nothing else, to avoid skipping side-effects. Especially, the following re-export is not followed:
import { foo } from "./foo.js"; export { foo as fooOriginal }; // Not followed :( export const fooWrapped = wrap(foo);
You should modify it into a regular re-export:
import { foo } from "./foo.js"; export { foo as fooOriginal } from "./foo.js"; // Followed! :) export const fooWrapped = wrap(foo);
Any code that can't be expressed like that, is dependant on side-effects and therefore can't be safely tree-shaken.
Usage
Install it to your devDependencies
:
# if you use npm
$ npm install --save-dev rollup-plugin-chunk-per-export
# if you use yarn
$ yarn add --dev rollup-plugin-chunk-per-export
And add it to your rollup.config.mjs
import { defineConfig } from "rollup";
+import chunkPerExport from "rollup-plugin-chunk-per-export";
export default defineConfig({
// ... your config here
plugins: [
// ...other plugins...
+ chunkPerExport(),
],
});