@nuxt/docs-nightly 4.1.0-29272761.6c974f0b → 4.1.0-29272968.ece1216a
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -637,3 +637,36 @@ export default defineNuxtConfig({
|
|
|
637
637
|
}
|
|
638
638
|
})
|
|
639
639
|
```
|
|
640
|
+
|
|
641
|
+
## entryImportMap
|
|
642
|
+
|
|
643
|
+
By default, Nuxt improves chunk stability by using an import map to resolve the entry chunk of the bundle.
|
|
644
|
+
|
|
645
|
+
This injects an import map at the top of your `<head>` tag:
|
|
646
|
+
|
|
647
|
+
```html
|
|
648
|
+
<script type="importmap">{"imports":{"#entry":"/_nuxt/DC5HVSK5.js"}}</script>
|
|
649
|
+
```
|
|
650
|
+
|
|
651
|
+
Within the script chunks emitted by Vite, imports will be from `#entry`. This means that changes to the entry will not invalidate chunks which are otherwise unchanged.
|
|
652
|
+
|
|
653
|
+
::note
|
|
654
|
+
Nuxt smartly disables this feature if you have configured `vite.build.target` to include a browser that doesn't support import maps, or if you have configured `vite.build.rollupOptions.output.entryFileNames` to a value that does not include `[hash]`.
|
|
655
|
+
::
|
|
656
|
+
|
|
657
|
+
If you need to disable this feature you can do so:
|
|
658
|
+
|
|
659
|
+
```ts twoslash [nuxt.config.ts]
|
|
660
|
+
export default defineNuxtConfig({
|
|
661
|
+
experimental: {
|
|
662
|
+
entryImportMap: false
|
|
663
|
+
},
|
|
664
|
+
// or, better, simply tell vite your desired target
|
|
665
|
+
// which nuxt will respect
|
|
666
|
+
vite: {
|
|
667
|
+
build: {
|
|
668
|
+
target: 'safari13'
|
|
669
|
+
},
|
|
670
|
+
},
|
|
671
|
+
})
|
|
672
|
+
```
|