@nuxt/docs-nightly 5.0.0-29761062.f52ca306 → 5.0.0-29761125.c6a7d2b6
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.
|
@@ -543,6 +543,72 @@ Alternatively, Nuxt will prompt you to install it automatically the first time a
|
|
|
543
543
|
|
|
544
544
|
If your project does not use JSX, no changes are needed.
|
|
545
545
|
|
|
546
|
+
### `giget` Is Now Optional (Remote Layers)
|
|
547
|
+
|
|
548
|
+
🚦 **Impact Level**: Minimal
|
|
549
|
+
|
|
550
|
+
#### What Changed
|
|
551
|
+
|
|
552
|
+
`giget` is no longer installed by default. It is now an optional peer dependency of `@nuxt/kit`, needed only to download a layer that `extends` names by remote URL:
|
|
553
|
+
|
|
554
|
+
```ts [nuxt.config.ts]
|
|
555
|
+
export default defineNuxtConfig({
|
|
556
|
+
extends: ['github:my-org/my-theme'],
|
|
557
|
+
})
|
|
558
|
+
```
|
|
559
|
+
|
|
560
|
+
Local layers, layers in `~~/layers/`, and layers installed as packages are unaffected.
|
|
561
|
+
|
|
562
|
+
#### Reasons for Change
|
|
563
|
+
|
|
564
|
+
Most projects never extend from a remote source, so the downloader was being installed for everyone to serve a small minority. Downloading a layer at config-resolution time is also the least reproducible way to consume one: the fetch happens outside your package manager, so it is not in your lockfile and, unless you pin it yourself, not pinned to a revision.
|
|
565
|
+
|
|
566
|
+
#### Migration Steps
|
|
567
|
+
|
|
568
|
+
**Preferred: move the layer into `package.json`.** Every major package manager understands git URLs, so a remote layer can be a normal dependency. This puts it in your lockfile, pins it to an exact commit, and installs it alongside everything else:
|
|
569
|
+
|
|
570
|
+
```json [package.json]
|
|
571
|
+
{
|
|
572
|
+
"devDependencies": {
|
|
573
|
+
"my-theme": "github:my-org/my-theme#4a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b"
|
|
574
|
+
}
|
|
575
|
+
}
|
|
576
|
+
```
|
|
577
|
+
|
|
578
|
+
Then extend from it by package name:
|
|
579
|
+
|
|
580
|
+
```ts [nuxt.config.ts]
|
|
581
|
+
export default defineNuxtConfig({
|
|
582
|
+
extends: ['my-theme'],
|
|
583
|
+
})
|
|
584
|
+
```
|
|
585
|
+
|
|
586
|
+
The part after `#` is any commit-ish, so a tag (`#v1.2.0`) or `#semver:^1.2.0` works too; a full commit SHA is the only form that is genuinely immutable.
|
|
587
|
+
|
|
588
|
+
**Otherwise, install `giget`** and keep using a remote `extends` entry:
|
|
589
|
+
|
|
590
|
+
::code-group{sync="pm"}
|
|
591
|
+
|
|
592
|
+
```bash [npm]
|
|
593
|
+
npm install -D giget
|
|
594
|
+
```
|
|
595
|
+
|
|
596
|
+
```bash [yarn]
|
|
597
|
+
yarn add -D giget
|
|
598
|
+
```
|
|
599
|
+
|
|
600
|
+
```bash [pnpm]
|
|
601
|
+
pnpm add -D giget
|
|
602
|
+
```
|
|
603
|
+
|
|
604
|
+
```bash [bun]
|
|
605
|
+
bun add -D giget
|
|
606
|
+
```
|
|
607
|
+
|
|
608
|
+
::
|
|
609
|
+
|
|
610
|
+
If a remote layer is resolved without `giget` present, Nuxt reports which `extends` entry needs it.
|
|
611
|
+
|
|
546
612
|
### Removal of Legacy `_renderResponse` Support
|
|
547
613
|
|
|
548
614
|
🚦 **Impact Level**: Minimal
|