Skip to content
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

Does anybody got this error too? #282

Open
ConstantineAlexandre opened this issue Mar 27, 2024 · 2 comments
Open

Does anybody got this error too? #282

ConstantineAlexandre opened this issue Mar 27, 2024 · 2 comments

Comments

@ConstantineAlexandre
Copy link

npm version 10.4.0

Screenshot from 2024-03-28 02-20-23

@madhavdutta
Copy link

madhavdutta commented Apr 4, 2024

Run : rm -rf ./node_modules
rm pnpm-lock.yaml

Add ^ symbol to install the latest version of the next and others, it will fix the issue.

Example :
"contentlayer": "^0.3.1",
"date-fns": "^2.29.3",
"lucide-react": "^0.92.0",
"next": "^13.3.2-canary.13",

Run : pnpm i

@Satyansh-07
Copy link

Just run pnpm add next@latest and you'll be good to go. Happy coding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants