Error with latest Next.js Project
Unanswered
Cuvier’s Dwarf Caiman posted this in #help-forum
Cuvier’s Dwarf CaimanOP
Error: Cannot find module '@tailwindcss/oxide-win32-x64-msvc'
i've tried installing these steps below:
Install Microsoft Visual C++ Redistribution Runtime Latest Version
Install Latest Node.js version
still receiving the same error when trying to run the fresh clean project.
i've tried installing these steps below:
Install Microsoft Visual C++ Redistribution Runtime Latest Version
Install Latest Node.js version
still receiving the same error when trying to run the fresh clean project.
73 Replies
Cuvier’s Dwarf CaimanOP
Cuvier’s Dwarf CaimanOP
bump
@Cuvier’s Dwarf Caiman bump
Dutch
can you share a vscode live share link via f1 > start collab...
Are you getting this error after upgrading tailwind to the latest version? Or this happens as soon as you create a new project, without touching anything?
For the former try to delete the
For the former try to delete the
.next
and node_modules
. For the latter, that’s weird, we need more context to help.@Cuvier’s Dwarf Caiman Error: Cannot find module '@tailwindcss/oxide-win32-x64-msvc'
i've tried installing these steps below:
Install Microsoft Visual C++ Redistribution Runtime Latest Version
Install Latest Node.js version
still receiving the same error when trying to run the fresh clean project.
can you share where are you importing this lib?
@LuisLl Are you getting this error after upgrading tailwind to the latest version? Or this happens as soon as you create a new project, without touching anything?
For the former try to delete the `.next` and `node_modules`. For the latter, that’s weird, we need more context to help.
Cuvier’s Dwarf CaimanOP
as soon as i create a new project, i’ve tried deleting node_modules. i’ll be on my pc soon to give more context to help!
i also have have tried creating a new project multiple time’s
Cuvier’s Dwarf CaimanOP
@LuisLl what kind of context do you need?
it only works for me in next.js 14.1.0 without turbopack, etc
it's kind of strange
This is weird because I just made a new project from scratch on version 15.2.2 with turbopack and it works fine for me.
@Cuvier’s Dwarf Caiman i also have have tried creating a new project multiple time’s
If it’s a new project can you push it to a public repo and I’ll clone it, to try it locally
@LuisLl If it’s a new project can you push it to a public repo and I’ll clone it, to try it locally
Cuvier’s Dwarf CaimanOP
yes, give me a minute
@Cuvier’s Dwarf Caiman yes, give me a minute
Cuvier’s Dwarf CaimanOP
see even when i try to create a new one it'll take FOREVER
and it'll stay like this
i just don't understand what's happening
do i just throw my whole pc away
when i create it and say NO to app router it'll create it....? @LuisLl i'm making a repo and i'll send the link here
@Cuvier’s Dwarf Caiman do i just throw my whole pc away
Yes that should solve it 🤣
@LuisLl Yes that should solve it 🤣
Cuvier’s Dwarf CaimanOP
nah fr lmfao
@Cuvier’s Dwarf Caiman when i create it and say NO to app router it'll create it....? <@744377057139753020> i'm making a repo and i'll send the link here
Well you’ll get the pages/ router instead, which is the router from version 12 and before.
there ya go
@LuisLl Well you’ll get the pages/ router instead, which is the router from version 12 and before.
Cuvier’s Dwarf CaimanOP
yeah just strange it's doing that as well...
@Cuvier’s Dwarf Caiman https://github.com/kiryano/test
It's not public is it? I get 404
@LuisLl It's not public is it? I get 404
Cuvier’s Dwarf CaimanOP
it is public
weird..
Cuvier’s Dwarf CaimanOP
wait
let me see
Cuvier’s Dwarf CaimanOP
oops my bad making it public
@LuisLl it's public now
@Krishna can you share where are you importing this lib?
Cuvier’s Dwarf CaimanOP
it's a new project so wherever it's being imported
i've even tried installing it, installing a different version of node.js and the runtime's
since people "claimed" it worked...
Cuvier’s Dwarf CaimanOP
could it be something that's installed wrong on my pc
versions, something?
idk what i'm missing
@Cuvier’s Dwarf Caiman Click to see attachment
This error was shown in a project using the app/ router tho, the one you uploaded to github is using pages/ router.
But you say the same error happens, right?
Cuvier’s Dwarf CaimanOP
yes
regardless
i can't use app router that's the issue as well
but i can use pages/ router
but yeah i still get that
"Error: Cannot find module '@tailwindcss/oxide-win32-x64-msvc'"
"Error: Cannot find module '@tailwindcss/oxide-win32-x64-msvc'"
Honestly I don't have any idea. I just cloned your repo, executed
pnpm install
and then pnpm dev
. All worked as expectedCuvier’s Dwarf CaimanOP
let me try that rq
wtf.
@LuisLl that worked
LOL
but when i do npm install it doesn't??????!
pnpm is just better i guess...
But it shouldn't be.. I don't think
npm
is broken, si it? lol pnpm
is just more performant, npm
is the default, it should work the same way:/okay it does work
i guess the pnpm install fixed it
but when i was trying npm install it didn't work
that's so odd?
@Cuvier’s Dwarf Caiman Click to see attachment
Look at this, I deleted the node_modules and these won't delete... funny enough it's the same package that was giving you problems earlier..
@LuisLl Look at this, I deleted the node_modules and these won't delete... funny enough it's the same package that was giving you problems earlier..
Cuvier’s Dwarf CaimanOP
what the heck?!
dude that's so weird
something should be fixed because that's very odd
i mean i'm sure that doesn't happen to everyone but for the few people it'd really complicated
Okay, when you delete the
.next
folder and node_modules
make sure the app is not running or you have a terminal session open in the same path. I closed my terminal and I let me delete the whole node_modules
now.and then it worked when reinstalling?
Yes, now I installed the packages with npm
Most weird issues like these solve by deleting
.next
folder and node_modules
. Make sure to make a clean installation, maybe you had the broken node_modules
when you installed your packages or ran the app. Otherwise it doesn't make sense to me:/@LuisLl Most weird issues like these solve by deleting `.next` folder and `node_modules`. Make sure to make a clean installation, maybe you had the broken `node_modules` when you installed your packages or ran the app. Otherwise it doesn't make sense to me:/
Cuvier’s Dwarf CaimanOP
yeah well thank you so much
You're welcome! I don't feel I did anything tho.. this issue was weird. Anyway, glad you got it working now.
@Cuvier’s Dwarf Caiman mark the solution when you can!