Issue : Pre-transform error: Missing "#internal/nuxt/paths" specifier in "nuxt" package (x2)
Hi,
Since this evening, i've got this error when i try to execute "npm run dev".
I've updated my Nuxt 3 version from 3.10.2 to 3.12.2 and cleaned my /nuxt, .package-lock.json etc but nothing fix it...
Do someone know how to fix it ?
Thank you for your help !
23 Replies
Can't anyone help me ?
Do you have a reproduction?
Hi ! What do you want to mean with reproduction ? 😅
creating a small repo with nothing but the isolated incident so we can peak at the code
Oh okay i will do it thank you !
Hey, this is my repo !
https://github.com/timotheduflos/nuxt_incident
If you need more information or anything else, don't hesitate to dm me 😁
GitHub
GitHub - timotheduflos/nuxt_incident
Contribute to timotheduflos/nuxt_incident development by creating an account on GitHub.
couldn't reproduce on my machine. Maybe check if your node version is the stable one ?
Your npm run dev works fine ? My is v.22.3.0
so not this either
I've updated all I can like nuxt, node, packages etc 😅
npm install && npm dev no error, just 2 warnings about imports of defineEmits and defineProps being uneccessary iirc
OKay... strange... I've checked to change HEAD of git commit to see a difference but i've got the same problem. Your response goes in the same way i think, maybe node problem
but I use the same node -v
Oh xD
I've tryed etc too
I don't know if there's a link with a possible node problem, but did you get that too when you did the npm install?
Humm I don't know where to search ^^"
Delete the .nuxt folder
And node module then reinstall everything-> npm run dev
@magius I made :
and always the same problem :
okay, I've done a little investigating and it looks like it's the i18n module that's making everything go wrong. I installed vue-i18n via npm, created an i18n.js plugin and once everything was reconfigured in my components everything seemed fine. However, I don't know why the nuxt i18n module bugs... Thank you very much for your help
do you eventually have globally installed packages that would ruin your experience ?
I don't think so, as you can see from the repo, the project is and will be fairly lightweight so I don't see why there should be any conflicts with so few packages installed ^^"
could you try in a Docker ?