Support NextJS 14

[bgub]

npm ERR! code ERESOLVE
--
14:57:32.907 | npm ERR! ERESOLVE could not resolve
14:57:32.908 | npm ERR!
14:57:32.908 | npm ERR! While resolving: next-contentlayer@0.3.4
14:57:32.908 | npm ERR! Found: next@14.0.0
14:57:32.908 | npm ERR! node_modules/next
14:57:32.908 | npm ERR!   next@"^14.0.0" from the root project
14:57:32.908 | npm ERR!
14:57:32.908 | npm ERR! Could not resolve dependency:
14:57:32.908 | npm ERR! peer next@"^12 \|\| ^13" from next-contentlayer@0.3.4
14:57:32.908 | npm ERR! node_modules/next-contentlayer
14:57:32.909 | npm ERR!   next-contentlayer@"^0.3.4" from the root project
14:57:32.909 | npm ERR!
14:57:32.909 | npm ERR! Conflicting peer dependency: next@13.5.6
14:57:32.909 | npm ERR! node_modules/next
14:57:32.909 | npm ERR!   peer next@"^12 \|\| ^13" from next-contentlayer@0.3.4
14:57:32.909 | npm ERR!   node_modules/next-contentlayer
14:57:32.909 | npm ERR!     next-contentlayer@"^0.3.4" from the root project

[Shubhdeep12]

cc @schickling

[marcofranssen]

For me it only fails when running with next dev --turbo.

[bgub]

@marcofranssen it runs fine for me too, but when I run npm i from scratch, it'll cause a Vercel build to fail (see #576)

[Fionn96]

For me it only fails when running with next dev --turbo.

Me too hope fix it.

[weichunnn]

Same error as @nebrelbug faced, I 'resolved' in the short term by:

• using npm install --force; OR
• downgrading to next.js 13

[mohsentaleb]

Until people get this fixed you can add --legacy-peer-deps to your npm i and proceed with your installation.

npm install contentlayer next-contentlayer date-fns --legacy-peer-deps

[januarionclx]

I believe that not only support should be added but errors should be replaced for warnings to avoid builds failing.

Like, in this specific case, if it wasn't throwing but showing a warning instead, we wouldn't be having this issue.

Support would be requested, yes, but wouldn't be critical as it is of now 🥲

[marcofranssen]

I believe that not only support should be added but errors should be replaced for warnings to avoid builds failing.

Like, in this specific case, if it wasn't throwing but showing a warning instead, we wouldn't be having this issue.

Support would be requested, yes, but wouldn't be critical as it is of now 🥲

This is the NPM ecosystem throwing the errors. Nothing this project can do about that.

[januarionclx]

I believe that not only support should be added but errors should be replaced for warnings to avoid builds failing.
Like, in this specific case, if it wasn't throwing but showing a warning instead, we wouldn't be having this issue.
Support would be requested, yes, but wouldn't be critical as it is of now 🥲

This is the NPM ecosystem throwing the errors. Nothing this project can do about that.

Is there a way to prevent this? I find this somewhat dangerous, it literally blocks the production builds (in this case, for no reason, basically above my own will).

[tunedsphere]

Any news related to this issue? Has it been fixed yet ?

[XahidEx]

Unexpected scalar at node end at line 4, column 201: (like this).
This error occurs when I'm adding a new mdx. Even if It's simple as this:

---
title: 'test'
publishedAt: '2023-12-12'
summary: 'test'
---

Test

Only facing this issue when I'm using the latest contentlayer. (I'm using nextjs14)

[josipledic]

+1 for nextjs14 support. It works fine so it shouldn't be hard to clean up the dependency requirements of the package.

[swe]

Just use the "next": "latest", at your package.json file, and it will be updated

[tunedsphere]

For the ones looking for a fix!

I was using npm and merge to pnpm! it did the trick for me!

[Gerald-ux-ux]

Yeah definitely downgrade to next 13 or 13.5.6