-
-
Notifications
You must be signed in to change notification settings - Fork 8
chore: upgraded playground to nuxt v3.16 in compat mode for nuxt 4 #161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Hey @colinscz , I +1'd it by updating it to the newest newest version of Nuxt, including the other packages. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good from my side, @alvarosabu could you verify/approve/merge it?
In any case we probably have to test it again with a nuxt project after the merge to see if the other issues were also resolved which you mentioned in the discord some time ago last year.
…onlyBuiltDeps for pnpm
the |
missing pnpm lock file: when updating to 10.7.0 or 10.7.1, pnpm should ask if recreating lock file and node_modules: press Y and when selected the deps after ... and then, commit and push pnpm lock file |
You are correct, It didn't produce or ask for a new one after updating to 10.7.1, weird.
Pushed the lock file! |
Upgraded the module to the latest version of Nuxt (3.16) with compat mode for Nuxt 4.
Fixed some additional minor stuff in the module.ts file.