cli
cli copied to clipboard
Upgrading to newest Nuxt version doesn't upgrade @nuxt/schema and @nuxt/kit?
Environment
- Operating System:
Darwin
- Node Version:
v22.9.0
- Nuxt Version:
3.13.2
- CLI Version:
3.14.0
- Nitro Version:
2.9.7
- Package Manager:
[email protected]
- Builder:
-
- User Config:
-
- Runtime Modules:
-
- Build Modules:
-
Reproduction
https://stackblitz.com/edit/github-7zuwfa?file=package.json
Describe the bug
Running npm run dev
after upgrading nuxt with npx nuxi@latest upgrade --force
gives the following warnings:
WARN [nuxt] Expected @nuxt/schema to be at least 3.13.2 but got 3.11.1. This might lead to unexpected behavior. Check your package.json or refresh your lockfile. 5:00:28 PM
WARN [nuxt] Expected @nuxt/kit to be at least 3.13.2 but got 3.11.1. This might lead to unexpected behavior. Check your package.json or refresh your lockfile.
However, the example I have on StackBlitz doesn't produce the issue we're having with our project. I'm not sure why. I've removed node_modules
and package-lock.json
and reinstalled everything with npm i
, I didn't remove node_modules
nor package-lock.json
and just did npm ci
, I ran just npm up
, and I finally ran npx nuxi@latest upgrade --force
and the warning still comes up. Maybe this is an issue with npm itself? nuxi
does say it's refreshing the package-lock.json
, but apparently it's not as made apparent by the messages being displayed.
Additional context
Like I mentioned previously I didn't run npx nuxi@latest upgrade --force
at first, but I thought it would be the last thing to fix this issue. It's not the end of the world, but it's certainly curious.
Logs
> dev
> nuxi dev
Nuxt 3.13.2 with Nitro 2.9.7 5:00:24 PM
5:00:25 PM
➜ Local: http://127.0.0.1:3000/
➜ Network: use --host to expose
WARN [nuxt] Expected @nuxt/schema to be at least 3.13.2 but got 3.11.1. This might lead to unexpected behavior. Check your package.json or refresh your lockfile. 5:00:28 PM
WARN [nuxt] Expected @nuxt/kit to be at least 3.13.2 but got 3.11.1. This might lead to unexpected behavior. Check your package.json or refresh your lockfile. 5:00:28 PM
ℹ Using Tailwind CSS from ~/assets/css/style.css nuxt:tailwindcss 5:00:28 PM
➜ DevTools: press Shift + Option + D in the browser (v1.5.2) 5:00:30 PM
ℹ Tailwind Viewer: http://127.0.0.1:3000/_tailwind/ nuxt:tailwindcss 5:00:30 PM
✔ Vite client built in 65ms 5:00:32 PM
✔ Vite server built in 336ms