Support NextJS 14 #575

nebrelbug · 2023-10-26T21:03:43Z

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: [email protected]
14:57:32.908 | npm ERR! Found: [email protected]
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 [email protected]
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: [email protected]
14:57:32.909 | npm ERR! node_modules/next
14:57:32.909 | npm ERR!   peer next@"^12 \|\| ^13" from [email protected]
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

The text was updated successfully, but these errors were encountered:

Shubhdeep12 · 2023-10-27T03:53:53Z

cc @schickling

marcofranssen · 2023-10-27T11:55:01Z

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

nebrelbug · 2023-10-27T16:46:18Z

@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 · 2023-10-28T14:52:56Z

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

Me too hope fix it.

weichunnn · 2023-10-30T01:46:46Z

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

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

mohsentaleb · 2023-10-30T17:42:23Z

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 · 2023-10-31T16:02:35Z

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 · 2023-10-31T16:36:53Z

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 · 2023-10-31T23:38:13Z

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 · 2023-11-03T12:12:34Z

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

XahidEx · 2023-11-04T07:40:00Z

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 · 2023-11-04T18:56:23Z

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

swe · 2023-11-17T02:43:28Z

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

tunedsphere · 2023-11-18T17:10:26Z

For the ones looking for a fix!

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

Gerald-ux-ux · 2023-11-21T13:02:59Z

Yeah definitely downgrade to next 13 or 13.5.6

agonist · 2023-11-22T00:29:36Z

No issues seems to be addressed and PR merged, is the project dying and we should consider other options?

willmruzek · 2023-11-23T01:22:11Z

Looks like 3 options until this issue is addressed:

npm install --force
npm install contentlayer next-contentlayer date-fns --legacy-peer-deps
Downgrade to Next 13

Ran into the below with both Next 13 and 14. If you install [email protected] and [email protected], the warning/error goes away.

<w> [webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] Parsing of /Users/mruzekw/Code/willmruzekdotcom/node_modules/@contentlayer/core/dist/dynamic-build.js for build dependencies failed at 'import(`file://${compiledConfigPath}`)'.
<w> Build dependencies behind this expression are ignored and might cause incorrect cache invalidation.
<w> [webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] Parsing of /Users/mruzekw/Code/willmruzekdotcom/node_modules/@contentlayer/core/dist/getConfig/index.js for build dependencies failed at 'import(`file://${modulePath}?x=${Date.now()}`)'.
<w> Build dependencies behind this expression are ignored and might cause incorrect cache invalidation.
<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: Can't resolve 'markdown-wasm/dist/markdown.node.js' in '/Users/mruzekw/Code/willmruzekdotcom/node_modules/@contentlayer/core/dist/markdown'
<w> while resolving 'markdown-wasm/dist/markdown.node.js' in /Users/mruzekw/Code/willmruzekdotcom/node_modules/@contentlayer/core/dist/markdown as file
<w>  at resolve esm file markdown-wasm/dist/markdown.node.js
<w>  at file dependencies /Users/mruzekw/Code/willmruzekdotcom/node_modules/@contentlayer/core/dist/markdown/markdown.js
<w>  at file /Users/mruzekw/Code/willmruzekdotcom/node_modules/@contentlayer/core/dist/markdown/markdown.js
<w>  at resolve esm file ./markdown/markdown.js
<w>  at file dependencies /Users/mruzekw/Code/willmruzekdotcom/node_modules/@contentlayer/core/dist/index.js
<w>  at file /Users/mruzekw/Code/willmruzekdotcom/node_modules/@contentlayer/core/dist/index.js
<w>  at resolve esm file @contentlayer/core
<w>  at file dependencies /Users/mruzekw/Code/willmruzekdotcom/node_modules/next-contentlayer/dist/plugin.js
<w>  at file /Users/mruzekw/Code/willmruzekdotcom/node_modules/next-contentlayer/dist/plugin.js
<w>  at resolve esm file ./plugin.js
<w>  at file dependencies /Users/mruzekw/Code/willmruzekdotcom/node_modules/next-contentlayer/dist/index.js
<w>  at file /Users/mruzekw/Code/willmruzekdotcom/node_modules/next-contentlayer/dist/index.js
<w>  at resolve esm file next-contentlayer
<w>  at file dependencies /Users/mruzekw/Code/willmruzekdotcom/next.config.mjs
<w>  at file /Users/mruzekw/Code/willmruzekdotcom/next.config.mjs
<w>  at resolve commonjs /Users/mruzekw/Code/willmruzekdotcom/next.config.mjs

emmalexandria · 2023-11-29T16:34:02Z

Looks like 3 options until this issue is addressed:

@piotrszubert pointed out this solution in another thread on this issue, which is to put this in your package.json:

"overrides": {
    "next-contentlayer": {
      "next": "$next"
    }
  },

Personally, I think it's the cleanest solution.

alamenai · 2023-12-02T18:52:29Z

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

Is it recommended for production?

emmalexandria · 2023-12-03T03:42:26Z

Is it recommended for production?

All of these fixes are somewhat janky. They bypass the error without resolving the underlying issue. If stability in your production environment is really critical it seems best to downgrade your Next version instead.

Otherwise, I think --force is better, as:

--legacy-peer-deps ignores all peer dependencies entirely and just installs the package.
--force makes changes to dependency versions if there's a conflict.

(I'm no expert on NPM)

nicolasgomeztoua · 2024-01-09T17:38:07Z

any news on this? if the code is open source we can just PR the change

marcofranssen · 2024-01-12T14:43:20Z

any news on this? if the code is open source we can just PR the change

Yeah, but even current open PRs are not handled. And who is going to cut releases so people can get a new version? :(

Or they are closed by a bot #556

nicolasgomeztoua · 2024-01-12T14:44:30Z

https://www.codemotion.com/magazine/frontend/how-to-create-an-mdx-blog-in-typescript-with-next-js/

Here bro come follow this guide and just build your own components

elie222 · 2024-01-16T23:46:41Z

This is how I migrated from ContentLayer to Next MDX:
elie222/inbox-zero@cf42b0b (#79)

Was tired of wrestling with this library :(

phukon · 2024-01-23T15:38:12Z

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)

@XahidEx just change the line endings for your mdx file from CRLF to LF. It's an old issue for contentlayer, cuz Windows uses CRLF endings.

AnweshGangula · 2024-01-28T13:49:27Z

Contentlayer is probably not being maintained anymore as per this issue: #429

temrb · 2024-02-18T20:34:02Z

yea i cant move on using contentlayer anymore even though it was an excellent solution!

for anyone that is looking for other alternatives: I'm now using mintlify free plan. for my usecase of just having blog posts setting this up was super simple! it also comes with lots of helpful components as well

cpatti97100 · 2024-03-19T15:19:36Z

Looks like 3 options until this issue is addressed:

@piotrszubert pointed out this solution in another thread on this issue, which is to put this in your package.json:
"overrides": {
    "next-contentlayer": {
      "next": "$next"
    }
  },
Personally, I think it's the cleanest solution.

is there something I should pay particular attention to when using this solution?

emmalexandria · 2024-03-23T11:52:45Z

Looks like 3 options until this issue is addressed:

@piotrszubert pointed out this solution in another thread on this issue, which is to put this in your package.json:
"overrides": {
    "next-contentlayer": {
      "next": "$next"
    }
  },
Personally, I think it's the cleanest solution.
is there something I should pay particular attention to when using this solution?

What it's doing is pretty simple. It's basically overriding Contentlayer's desired version of Next to whatever you have installed. The main thing to be aware of is that this only works because Contentlayer doesn't actually have any compatibility issues with NextJS 14. However, in the future it may indeed actually break and this fix won't do anything.

nickzelei · 2024-05-10T15:02:34Z

This is becoming more critical due to a recent CVE CVE-2024-34351

aimahusnain · 2024-06-21T12:21:54Z

Locally, we can use the -force option to run it, but what should we do during deployment?

nicolasgomeztoua · 2024-06-21T16:04:47Z

Locally, we can use the -force option to run it, but what should we do during deployment?

You can edit your package installation command on Vercel.

And if you are deploying somewhere else you always have control over than anyways,
but seriously as I've said above, why bother putting a deprecated package in your project. Especially with other options

nebrelbug · 2024-07-02T01:04:33Z

I highly recommend switching over to https://github.com/sdorra/content-collections. I was able to switch over quite easily and Zod schemas are super nice. Feature parity seems completely on par with Contentlayer.

stale · 2024-09-01T04:09:30Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

aimahusnain · 2024-09-01T05:01:28Z

I highly recommend switching over to https://github.com/sdorra/content-collections. I was able to switch over quite easily and Zod schemas are super nice. Feature parity seems completely on par with Contentlayer.

Hi, can we use content collections in next.js latest versions?

stale · 2024-11-05T00:49:48Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Romstar mentioned this issue Oct 27, 2023

added next.js 14 support #576

Closed

januarionclx mentioned this issue Oct 31, 2023

[Refactor requests] version warnings should be warnings instead of errors. #581

Closed

jkeussen mentioned this issue Nov 21, 2023

Compatibility issues. #606

Closed

fraune mentioned this issue Nov 23, 2023

next-contentlayer installation ERROR in next 14.0.3 on terminal #605

Closed

rosszurowski mentioned this issue Dec 2, 2023

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 #607

Closed

This was referenced Feb 2, 2024

Update packages timlrx/contentlayer2#1

Merged

Update packages #638

Closed

sarahgm mentioned this issue Mar 12, 2024

test shiki update marigold-ui/marigold#3808

Closed

stale bot added the meta: stale label Sep 1, 2024

stale bot removed the meta: stale label Sep 1, 2024

stale bot added the meta: stale label Nov 5, 2024

stale bot closed this as completed Nov 16, 2024

Support NextJS 14 #575

Support NextJS 14 #575

Comments

nebrelbug commented Oct 26, 2023

Shubhdeep12 commented Oct 27, 2023

marcofranssen commented Oct 27, 2023

nebrelbug commented Oct 27, 2023

Fionn96 commented Oct 28, 2023

weichunnn commented Oct 30, 2023 • edited Loading

mohsentaleb commented Oct 30, 2023

januarionclx commented Oct 31, 2023

marcofranssen commented Oct 31, 2023

januarionclx commented Oct 31, 2023

tunedsphere commented Nov 3, 2023

XahidEx commented Nov 4, 2023

josipledic commented Nov 4, 2023

swe commented Nov 17, 2023

tunedsphere commented Nov 18, 2023

Gerald-ux-ux commented Nov 21, 2023

agonist commented Nov 22, 2023

willmruzek commented Nov 23, 2023 • edited Loading

emmalexandria commented Nov 29, 2023

alamenai commented Dec 2, 2023

emmalexandria commented Dec 3, 2023 • edited Loading

nicolasgomeztoua commented Jan 9, 2024

marcofranssen commented Jan 12, 2024 • edited Loading

nicolasgomeztoua commented Jan 12, 2024

elie222 commented Jan 16, 2024

phukon commented Jan 23, 2024 • edited Loading

AnweshGangula commented Jan 28, 2024

temrb commented Feb 18, 2024

cpatti97100 commented Mar 19, 2024

emmalexandria commented Mar 23, 2024

nickzelei commented May 10, 2024 • edited Loading

aimahusnain commented Jun 21, 2024

nicolasgomeztoua commented Jun 21, 2024

nebrelbug commented Jul 2, 2024

stale bot commented Sep 1, 2024

aimahusnain commented Sep 1, 2024

stale bot commented Nov 5, 2024

weichunnn commented Oct 30, 2023 •

edited

Loading

willmruzek commented Nov 23, 2023 •

edited

Loading

emmalexandria commented Dec 3, 2023 •

edited

Loading

marcofranssen commented Jan 12, 2024 •

edited

Loading

phukon commented Jan 23, 2024 •

edited

Loading

nickzelei commented May 10, 2024 •

edited

Loading