You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat: add `codeSplitJs` option
* fix: only use `manualChunks` when `!codeSplitJS`
* Create beige-carpets-wave.md
* chore: regenerate types
* chore: add option to `options` app for tests
* chore: move tests from `options` to `options-2` and add test for bundle
* chore: rename chunk, add css test
* chore: rename option to `codeSplit`
* chore: apply suggestions from code review
* this looks unintentional, reverting
* tweak docs
* DRY out
* get rid of Promise.all when codeSplit: false
* types
* rename to bundleStrategy
* more detail
* pretty sure this is unused
* tweak
* small tweaks
* inline strategy
* omit modulepreloads when inlining script
* regenerate
* fix
* changeset
* regenerate
* fix
* jsdoc
* allow trailing /index.html when serving from filesystem
* treat current directory as base when using hash-based routing
* make self-contained apps possible
* lint
* oops
---------
Co-authored-by: paoloricciuti <[email protected]>
Co-authored-by: Simon Holthausen <[email protected]>
* If `'split'`, splits the app up into multiple .js/.css files so that they are loaded lazily as the user navigates around the app. This is the default, and is recommended for most scenarios.
503
-
* If `'single'`, creates just one .js bundle and one .css file containing code for the entire app.
502
+
* - If `'split'`, splits the app up into multiple .js/.css files so that they are loaded lazily as the user navigates around the app. This is the default, and is recommended for most scenarios.
503
+
* - If `'single'`, creates just one .js bundle and one .css file containing code for the entire app.
504
+
* - If `'inline'`, inlines all JavaScript and CSS of the entire app into the HTML. The result is usable without a server (i.e. you can just open the file in your browser).
504
505
*
505
506
* When using `'split'`, you can also adjust the bundling behaviour by setting [`output.experimentalMinChunkSize`](https://rollupjs.org/configuration-options/#output-experimentalminchunksize) and [`output.manualChunks`](https://rollupjs.org/configuration-options/#output-manualchunks)inside your Vite config's [`build.rollupOptions`](https://vite.dev/config/build-options.html#build-rollupoptions).
* If `'split'`, splits the app up into multiple .js/.css files so that they are loaded lazily as the user navigates around the app. This is the default, and is recommended for most scenarios.
485
-
* If `'single'`, creates just one .js bundle and one .css file containing code for the entire app.
484
+
* - If `'split'`, splits the app up into multiple .js/.css files so that they are loaded lazily as the user navigates around the app. This is the default, and is recommended for most scenarios.
485
+
* - If `'single'`, creates just one .js bundle and one .css file containing code for the entire app.
486
+
* - If `'inline'`, inlines all JavaScript and CSS of the entire app into the HTML. The result is usable without a server (i.e. you can just open the file in your browser).
486
487
*
487
488
* When using `'split'`, you can also adjust the bundling behaviour by setting [`output.experimentalMinChunkSize`](https://rollupjs.org/configuration-options/#output-experimentalminchunksize) and [`output.manualChunks`](https://rollupjs.org/configuration-options/#output-manualchunks)inside your Vite config's [`build.rollupOptions`](https://vite.dev/config/build-options.html#build-rollupoptions).
0 commit comments