Per output chunking

.lintstagedrc

@@ -3,7 +3,7 @@
     "prettier --write",
     "tslint --project . --fix"
   ],
-  "test/**/*.ts": [
+  "test/typescript/**/*.ts": [
     "prettier --write",
     "tslint --project test/typescript --fix"
   ],

docs/01-command-line-reference.md

@@ -35,11 +35,8 @@ export default { // can be an array (for multiple inputs)
 
   // advanced input options
   cache,
-  inlineDynamicImports,
-  manualChunks,
   onwarn,
   preserveEntrySignatures,
-  preserveModules,
   strictDeprecations,
 
   // danger zone
@@ -73,11 +70,14 @@ export default { // can be an array (for multiple inputs)
     extend,
     footer,
     hoistTransitiveImports,
+    inlineDynamicImports,
     interop,
     intro,
+    manualChunks,
     minifyInternalExports,
     outro,
     paths,
+    preserveModules,
     sourcemap,
     sourcemapExcludeSources,
     sourcemapFile,

docs/02-javascript-api.md

@@ -83,11 +83,8 @@ const inputOptions = {
 
   // advanced input options
   cache,
-  inlineDynamicImports,
-  manualChunks,
   onwarn,
   preserveEntrySignatures,
-  preserveModules,
   strictDeprecations,
 
   // danger zone
@@ -129,11 +126,14 @@ const outputOptions = {
   externalLiveBindings,
   footer,
   hoistTransitiveImports,
+  inlineDynamicImports,
   interop,
   intro,
+  manualChunks,
   minifyInternalExports,
   outro,
   paths,
+  preserveModules,
   sourcemap,
   sourcemapExcludeSources,
   sourcemapFile,

docs/04-tutorial.md

@@ -282,7 +282,7 @@ var version=function(){"use strict";var n="1.0.0";return function(){console.log(
 
 ### Code Splitting
 
-For code splitting, there are cases where Rollup splits code into chunks automatically, like dynamic loading or multiple entry points, and there is a way to explicitly tell Rollup which modules to split into separate chunks via the [`manualChunks`](guide/en/#manualchunks) option.
+For code splitting, there are cases where Rollup splits code into chunks automatically, like dynamic loading or multiple entry points, and there is a way to explicitly tell Rollup which modules to split into separate chunks via the [`output.manualChunks`](guide/en/#outputmanualchunks) option.
 
 To use the code splitting feature to achieve the lazy dynamic loading (where some imported module(s) is only loaded after executing a function), we go back to the original example and modify `src/main.js` to load `src/foo.js` dynamically instead of statically:
 

docs/06-faqs.md

@@ -61,7 +61,7 @@ With this optimization, a JavaScript engine will discover all transitive depende
 2. Load and parse `other-entry.js` and `external`. The import of `other-entry.js` is already loaded and parsed.
 3. Execute `main.js`.
 
-There may be situations where this optimization is not desired, in which case you can turn it off via the [`output.hoistTransitiveImports`](guide/en/#outputhoisttransitiveimports) option. This optimization is also never applied when using the [`preserveModules`](guide/en/#preservemodules) option.
+There may be situations where this optimization is not desired, in which case you can turn it off via the [`output.hoistTransitiveImports`](guide/en/#outputhoisttransitiveimports) option. This optimization is also never applied when using the [`output.preserveModules`](guide/en/#outputpreservemodules) option.
 
 #### How do I add polyfills to a Rollup bundle?
 
@@ -94,7 +94,7 @@ For most code this is not a problem, because Rollup can guarantee:
 This is however a problem for polyfills, as those usually need to be executed first but it is usually not desired to place an import of the polyfill in every single module. Luckily, this is not needed:
 
 1. If there are no external dependencies that depend on the polyfill, it is enough to add an import of the polyfill as first statement to each static entry point.
-2. Otherwise, additionally making the polyfill a separate entry or [manual chunk](guide/en/#manualchunks) will always make sure it is executed first.
+2. Otherwise, additionally making the polyfill a separate entry or [manual chunk](guide/en/#outputmanualchunks) will always make sure it is executed first.
 
 #### Is Rollup meant for building libraries or applications?
 

rollup.config.js

@@ -99,7 +99,8 @@ export default command => {
 		],
 		treeshake,
 		manualChunks: { rollup: ['src/node-entry.ts'] },
-		strictDeprecations: true,
+		// TODO set this to `true` again once manualChunks has been moved to the output
+		strictDeprecations: false,
 		output: {
 			banner,
 			chunkFileNames: 'shared/[name].js',