-
Notifications
You must be signed in to change notification settings - Fork 201
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
next-contentlayer installation ERROR in next 14.0.3 on terminal #605
Comments
I received this error when I ran |
@anthonyverducci change the next version to 13.4 it works |
@Sahad-09 the point is to use latest possible version - I've made a working (throwing warnings but working) setup with latest next and contentlayer, just force the installation |
@z4nr34l i see, Did people stop maintaining this repo ? It seems to be months ago so there might be some bug. |
I would also like to see support for Next.js 14 without having to force the installation. |
This issue is a dupe of #575 In the meantime, try |
add this in your package.json and then try install once again
|
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/next
npm ERR! next@"14.0.3" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer next@"^12 || ^13" from [email protected]
npm ERR! node_modules/next-contentlayer
npm ERR! next-contentlayer@"^0.3.4" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\Sahad\AppData\Local\npm-cache_logs\2023-11-23T07_19_34_982Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: C:\Users\Sahad\AppData\Local\npm-cache_logs\2023-11-23T07_19_34_982Z-debug-0.log
This error does not appear when I changed the version to next 13
The text was updated successfully, but these errors were encountered: