-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Nuxt version is specified to be 3.15.3, but resolving as 3.13.2 #30763
Comments
Do you get a warning message - is that the issue? |
No warnings, the project seems to start just fine There is a warning coming from Vitest when running tests though Plus I am getting error messages like this when trying to run E2E tests - I think it might be related to the old version of Nuxt being used
|
Is there something like a "local Nuxt cache" where the older version should have stuck? Because this is what happens when I try to initialize the fresh project using Version
|
So (with a help of ChatGPT) using
And among a
I followed that trail into my local Node.js installation and voila - in parent directory of my Node, there were some messed up installation of a Nuxt project with a version - who would say - 3.13.2 😅 So I deleted the files and all started working as expeted. I cant say I understand all the mechanics yet, but it was just my mess. Nothing is wrong with Nuxt itself. |
I have recently started a new project - https://github.com/AloisSeckar/nuxt-spec - it should serve as a base layer to provide testing functionality to my other apps. So I dont have to maintain a set of dependencies in each project separately.
As you can see in the
package.json
, the Nuxt version is specified to be the latest -3.15.3
:Compatibility date in
nuxt.config.ts
is set to2025-01-26
However, after fresh install (I already tried to delete all
node_modules
and also ranpnpm store prune
), usingpnpm dev
always resolves.nuxt
to version3.13.2
.I fail to understand where this comes from. I guess it is one of the other dependencies, but I don't see the pattern 🤔
The text was updated successfully, but these errors were encountered: