Automatic pack your dependency in a bundle, publish it to NPM, powered by esbuild and ncc.
Have you ever care about how many modules(files) your dependency are included, Autobundle help you make a bundle from your dependency, you just need import one module from. Or if you are a bundlephobia, this is exactly built for you.
- Pack all modules of dependency into one file
- Generally faster bootup time and less I/O overhead (in node platform or webpack/etc. bundler)
- Tree-shake your dependency
- Understand how large of your dependency
- Minimal node_modules
- You don't need to create new repository, new package, publish it, etc. Just for bundling job, it's easier with autobundle
Same bundlephobia.com, Autobundle use technology like esbuild, webpack to bundling your dependency and automatic publish to NPM registry.
Go to New Issue and request
- Note 1: We highly recommend you only bundling the dependency connect a little dependencies (or the core package), because all dependencies will put into the bundle. You should test again after bundling the package.
- Note 2: This will also power off the tree-shakeable of dependency.
- express@5.0.0-alpha.8: 806 kB
- express@4.17.1: 795 kB
- express@4.17.0: 797 kB
- express@4.16.4: 791 kB
- pg@8.7.1: 107 kB
- ms@1.0.0: 1.97 kB
- injection-js@2.4.0: 30.3 kB
- injection-js@2.3.2: 29.7 kB
- path-to-regexp@6.2.0: 6.01 kB
- @crawlo/graphql@1.0.28: 261 kB
- intl-number-input@1.0.0: 11.3 kB
- puppeteer-core@10.4.0: 403 kB
- puppeteer-core@1.7.0: 441 kB
- playwright-core@1.15.2: 1.15 MB
- class-validator@0.13.1: 313 kB
- graphql-request@3.6.0: 179 kB
- create definition file (d.ts) file (currently esbuild not supported)
- ncc engine
- flow: test if the generated package is installable
- "sideEffects" option
- comment the externals suggestion when failed
See Contributing