No `.contentlayer` folder is generated in Next.js 13.3

[qiushiyan]

Seems contentlayer is currently imcompatible with the latest version of Next.js 13.3, when I run next dev non .contentlayer folder is generated.

I cloned the package.json, next.config.js and contentlayer config file from the example project and run the following comand to update nextjs

pnpm add next@latest react@latest react-dom@latest

After this pnpm run dev does not generated the .contentlayer folder.

example repo

[cibulka]

Yes, having the same problem. Downgrading to 13.2.4 works, assuming you overwrote telemetry dependency as described here.

[kamtorocks]

Same problem, but downgrading to 13.2.4 will encounter other next problems, can anyone provide some help?

[kamtorocks]

I have found the cause of this problem.
Since next@v13.2.5-canary.27, next dev has been using jest-worker to start the service.

Using a version below next@v13.2.5-canary.26 will not have this problem.
Of course, the best solution is to optimize the way of next config plugin.

[nkilm]

what triggers the creation of .contentlayer folder? I have degraded my nextjs version to 13.2.4 from 13.3.0 but the folder is still not getting generated.

// next.config.js

/** @type {import('next').NextConfig} */
const { withContentlayer } = require("next-contentlayer");

const nextConfig = {
  reactStrictMode: true,
  distDir: "build",
  experimental: {
    appDir: true,
  },
};

module.exports = withContentlayer(nextConfig);

[haaarshsingh]

Just saw this issue. My contentlayer is working fine (check: harshhhdev/www), but it's because I'm using 0.3.0 instead of 0.3.1.

[sean-clayton]

Is this a bug with Next 13.3 or is it a bug with contentlayer?

[kamtorocks]

Is this a bug with Next 13.3 or is it a bug with contentlayer?

It's just a matter of how the plugin is started

[thara003]

I too have the same issue, here's my package.json

    "next": "13.3.0",
    "next-contentlayer": "^0.3.0",
    "contentlayer": "^0.3.0",

also tried downgrading the versions just like the contentlayer-example still the issue persist.

[millievn]

work fine with these configs( see my forked example ):

 "next": "13.2.4",
 "next-contentlayer": "0.3.1",
"contentlayer": "0.3.1"

[skwowet]

@qiwang97 these are same versions used in contentlayer-example, but still it doesn't work.

    "contentlayer": "^0.3.0",
    "next": "13.2.5-canary.16",
    "next-contentlayer": "^0.3.0",

I used the above example from leerob's portfolio repository and it works fine.

[TheBinaryGuy]

Until this is resolved, you can either use concurrently to work around this:

{
  // ---
  "scripts": {
    "dev": "concurrently \"contentlayer dev\" \"next dev\"",
    "build": "contentlayer build && next build"
  }
  / ---
}

Or have 2 different scripts for development and run them both in different tabs:

{
  // ---
  "scripts": {
    "cl-dev": "contentlayer dev",
    "dev": "next dev",
    "build": "contentlayer build && next build"
  }
  / ---
}

[gsen]

Local fix until this issue is resolved.
You can update the dev script in package.json and make use of the content layer cli as follows:

"scripts": {
    "dev": "contentlayer dev & next dev"
}

then run
pnpm dev

Content layer cli - https://www.contentlayer.dev/docs/reference/cli#dev