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

[alamenai]

Hi Contenlayer Team,

Thank you so much for this amazing solution. We really enjoy working with it.

Today, our build failed in the deployment environment and I found that the issue behind this is the version compatibility between NextJS 14 and the ContentLayer version.

In my local, I installed the dependency using legacy-peer-deps, and everything worked well, however, when I pushed the code and during the build time, I got this issue:

This my azure-pipeline.yml

# Node.js with React
# Build a Node.js project that uses React.
# Add steps that analyze code, save build artifacts, deploy, and more:
# https://docs.microsoft.com/azure/devops/pipelines/languages/javascript

trigger:
- main

pool:
  vmImage: ubuntu-latest

steps:
- task: NodeTool@0
  inputs:
    versionSource: 'spec'
    versionSpec: '10.x'
    checkLatest: true
  displayName: 'Install Node.js'

- script: |
    npm install
    npm run build
  displayName: 'npm install and build'

[ghost]

Try to install using npm install --force

[Chrismacolor]

Getting same error with NextJS 14. npm install --force every time is not a stable option. Any plans on fixing this?

[ghost]

Switch next.js to a supported version or fork this repository and update the package.

[alamenai]

I temporarily used npm install --lagacy-peer-deps but I faced issues with the CI/CD because you have to apply this also during the deployment process.

You have to force your installation with --leagcy-peer-deps by configuring your .npmrc:

legacy-peer-deps=true

[rosszurowski]

This is the same error that's captured in #575. Generally, the recommended way to solve it is with npm, yarn, or pnpm overrides, like is described in this comment.

[Sabir222]

@MenaiAla you are a life saver thanks the .npmrc solution worked i hope they update the next-contentlayer soon.