Is this normal create-next-app@latest behavior?
Answered
Chum salmon posted this in #help-forum
Chum salmonOP
So I did that
https://tailwindcss.com/docs/installation/framework-guides/nextjs
https://nextjs.org/docs/app/guides/tailwind-css
I never had to do that by the way but I did it anyway trying to play with it. It still doesn't work..
So I check package.json for Next and Tailwind version.
Even though I ran
That's super strange.
So I'm like let me try creating a new project the same version as my old ones (15.3.1) and see what happens.
The result: tailwind works perfectly as expected without an issue.
So I tried create next-app@latest again. This time I paid close attention to the terminal. Then I found it says
Does this mean if there is 1 critical vulnerability, it will give you different version of Next.js?
create-next-app@latest
to start a new project and I was just setting it up with css, lyaout and everything then I realize it doesn't work the way it should. More specifically, the color variables are not showing when I type in a component file (even after restarting vscode). So I double check Next and Tailwind docs and install Tailwind postcss like the docs say:https://tailwindcss.com/docs/installation/framework-guides/nextjs
https://nextjs.org/docs/app/guides/tailwind-css
I never had to do that by the way but I did it anyway trying to play with it. It still doesn't work..
So I check package.json for Next and Tailwind version.
Even though I ran
create-next-app@latest
The Next is 15.1.8 which is older than my previous projects (15.3.1)That's super strange.
So I'm like let me try creating a new project the same version as my old ones (15.3.1) and see what happens.
The result: tailwind works perfectly as expected without an issue.
So I tried create next-app@latest again. This time I paid close attention to the terminal. Then I found it says
1 critical vulnerability
Does this mean if there is 1 critical vulnerability, it will give you different version of Next.js?
Answered by Anay-208 | Ping in replies
don't use @latest for now, since the wrong version has been tagged