@nuxt/docs-nightly 5.0.0-29747984.affe36f4 → 5.0.0-29748075.a8f07670
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.
|
@@ -66,6 +66,7 @@ When you set your `future.compatibilityVersion` to `5`, defaults throughout your
|
|
|
66
66
|
- **Comment node placeholders**: Client-only components use [comment nodes instead of `<div>`](/docs/4.x/getting-started/upgrade#client-only-comment-placeholders) as SSR placeholders, fixing a scoped styles hydration issue
|
|
67
67
|
- **Stricter side-effect imports**: The generated `tsconfig.json` enables [`noUncheckedSideEffectImports`](/docs/4.x/getting-started/upgrade#stricter-side-effect-imports) to match the TypeScript 7 default
|
|
68
68
|
- **Vue Options API disabled**: The [Options API is compiled out of the client bundle](/docs/4.x/getting-started/upgrade#vue-options-api-disabled-by-default) to reduce its size
|
|
69
|
+
- **`process.*` type augmentation removed**: TypeScript no longer exposes [deprecated `process.*` flags](/docs/4.x/getting-started/upgrade#process-type-augmentation-removed) on `NodeJS.Process`
|
|
69
70
|
- Other Nuxt 5 improvements and changes as they become available
|
|
70
71
|
|
|
71
72
|
::note
|
|
@@ -74,6 +75,35 @@ This section is subject to change until the final release, so please check back
|
|
|
74
75
|
|
|
75
76
|
Breaking or significant changes will be noted below along with migration steps for backward/forward compatibility.
|
|
76
77
|
|
|
78
|
+
### `process.*` Type Augmentation Removed
|
|
79
|
+
|
|
80
|
+
🚦 **Impact Level**: Minimal
|
|
81
|
+
|
|
82
|
+
#### What Changed
|
|
83
|
+
|
|
84
|
+
Nuxt no longer augments `NodeJS.Process` with `browser`, `client`, `dev`, `server`, and `test`. Build-time defines for those flags remain for compatibility, but TypeScript will not treat them as known properties.
|
|
85
|
+
|
|
86
|
+
Prefer [`import.meta.*`](/docs/4.x/api/advanced/import-meta). Those flags are replaced at build time and stay tree-shakeable.
|
|
87
|
+
|
|
88
|
+
#### Migration Steps
|
|
89
|
+
|
|
90
|
+
Replace legacy checks in your app code, modules, and libraries:
|
|
91
|
+
|
|
92
|
+
```ts
|
|
93
|
+
// Before
|
|
94
|
+
// eslint-disable-next-line nuxt/prefer-import-meta
|
|
95
|
+
if (process.server) {
|
|
96
|
+
/* ... */
|
|
97
|
+
}
|
|
98
|
+
|
|
99
|
+
// After
|
|
100
|
+
if (import.meta.server) {
|
|
101
|
+
/* ... */
|
|
102
|
+
}
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
The [`nuxt/prefer-import-meta`](https://eslint.nuxt.com/packages/plugin#nuxtprefer-import-meta) ESLint rule flags remaining `process.*` usage.
|
|
106
|
+
|
|
77
107
|
### Case-Sensitive Routing
|
|
78
108
|
|
|
79
109
|
🚦 **Impact Level**: Minimal
|
|
@@ -18,6 +18,10 @@ Read more about `import.meta`.
|
|
|
18
18
|
|
|
19
19
|
These values are statically injected and can be used for tree-shaking your runtime code.
|
|
20
20
|
|
|
21
|
+
::note
|
|
22
|
+
`process.browser`, `process.client`, `process.dev`, `process.server`, and `process.test` were soft-deprecated in Nuxt 3.12. In Nuxt 5 or with `future.compatibilityVersion: 5`, Nuxt no longer augments `NodeJS.Process` with those properties. Prefer the matching `import.meta.*` flags; build-time `process.*` defines still exist for compatibility.
|
|
23
|
+
::
|
|
24
|
+
|
|
21
25
|
Property | Type | Description
|
|
22
26
|
--- | --- | ---
|
|
23
27
|
`import.meta.client` | boolean | True when evaluated on the client side.
|