docs: initial compatibility table and migration guide#208
docs: initial compatibility table and migration guide#208
Conversation
| - "nuxt-vite": "latest" | ||
| }, | ||
| "devDependencies": { | ||
| + "nuxt3": "latest" |
There was a problem hiding this comment.
I'm not sure to follow the purpose of this guide. Using nuxt2 and 3 dependencies in the same project??
There was a problem hiding this comment.
This is as nice idea to tell how prepare your nuxt2 projects for nuxt3 without risking unstable software but I guess it should not involve nuxt3 or wp5 but official compat features like nitro or app compostables.
There was a problem hiding this comment.
(This was meant to be a guide for how to migrate a nuxt2 project to nuxt3.)
There was a problem hiding this comment.
I think it's WAY early to write this guide (also we can discuss about some approaches. having two incompatible deps on same project is probably not best...)
| ``` | ||
|
|
||
|
|
||
| 5. Upgrade any webpack-ecosystem packages (loaders, plugins, etc.) to their webpack5 equivalents. For example, `sass-loader` can be upgraded to v12. |
There was a problem hiding this comment.
It will break nuxt2 using latest loaders. And no point for nuxt3..
|
|
||
| ### Work in progress | ||
|
|
||
| * [`@nuxt/content`](https://github.com/nuxt/content/) |
There was a problem hiding this comment.
Since this might be a rolling update, let's rethink about possible module tracking solutions :) (it would probably be nicer if we include such meta in nuxt/modules yml files or directly fetch from their pkg)
|
|
||
| 2. Upgrade your dependencies to the latest version supported by Nuxt 2, ensuring at each stage that your project is still working as intended. | ||
| 1. Install `core-js@3`. | ||
| 2. Install and enable [`nuxt-postcss8`](https://github.com/nuxt/postcss8) to migrate to PostCSS 8. |
There was a problem hiding this comment.
Since both corejs3 and postcss8 are planned for 2.16, it would probably be easier to omit from docs here and instead recommend upgrading to latest 2.x with proper upgrade guides in 2.x website (nuxt/website-v2#1434)
|
|
||
| | Name | Description | Nuxt 2 | Nuxt 3 | Migration steps required | | ||
| | --------------------- | ------------------ | ------ | ------ | -------------------------------------------------------------------------------------------------------------------- | | ||
| | `app.vue` | | ❌ | ✅ | Move `layouts/default.vue` (if present) to `~/app.vue` and rename the `<nuxt />` component to `<nuxt-page />` | |
There was a problem hiding this comment.
Let's keep it evolving in #191 to have better idea how it looks like. Probably for description, we can use actual sections with detailed step-by-step guide and tips.
pi0
force-pushed
the
main
branch
4 times, most recently
from
1aeb417 to
ee8eaef
Compare
|
Moving to #459 |
2 participants
this will need to be updated as we go
Note that this implements the nuxt/nuxt#11061 issue - and we can update the docs accordingly as part of any future PRs/feature improvements.
TODO: