Closed gb-beng closed 1 year ago
latest migration guide: https://nuxt.com/docs/migration/overview
as part of this migration we should move to Node version 18: https://github.com/beeldengeluid/labs.beeldengeluid.nl/issues/444
keeping track of my research and migration steps here:
__nuxt2
and moved everything there, except: .git
, and .editorconfig
npx nuxi init nuxt-app
then moved all files up from nuxt-app dir to rootWe now have a brand new nuxt3 template
npm install
npm run dev
getLocalePath()
. To start basic, I focus on EN locale only first, and leave NL locale TBD for later.[Vue warn]: Failed to resolve component: v-tabs-slider
, (found https://stackoverflow.com/questions/70719044/vue-warn-failed-to-resolve-component-v-toolbar-title-issue-vue3-and-vuetify, but we are adding Vuetify to nuxt as a plugin, so not 1 on 1 applicable). Possibly the v-tabs-slider
can be removed entirely in favour of using a v-tabs prop. leaving this for later as it's a non-breaking warning and tab slider functionality is fine. max-width: 100%
, as styled by /assets/scss/layout/markdown.scss
, but these styles aren't applid. Tried installing sass-loader
but didn't help.
nuxt-content
class name, adding this in manually on ContentRenderer
elements./public
dir/public
dir and updated components (for simplification)VisualMain
component is still throwing panzoom related warnings[eslint-plugin-vuetify](https://www.npmjs.com/package/eslint-plugin-vuetify/v/next)
to help fix a large part of deprecated Vuetify components.Philo & Govert Calling about plan of action status:
npm run lintfix
throws: (37 problems (36 errors, 1 warning))
VisualMain
component to be properly connected with PanZoom dependencyNew PR: https://github.com/beeldengeluid/labs.beeldengeluid.nl/pull/538
Next step: review with the team.
Also consider Nuxt Bridge
https://nuxt.com/vision-2023#migrating-to-nuxt-3
Would also resolve some of the security warnings we cannot resolve:
https://github.com/beeldengeluid/x-omgeving/issues/709