Error when building with contentlayer 0.3.4 and Next.js 13 App Router #506

schneedotdev · 2023-07-07T06:11:59Z

When I run `pnpm contentlayer build`, I run into an error within node_modules and cannot resolve it.

Versions

"contentlayer": "^0.3.4",
"next": "13.4.9",

Error Message

import { ConsoleSpanExporter, SimpleSpanProcessor } from "@opentelemetry/sdk-trace-base";
         ^^^^^^^^^^^^^^^^^^^
SyntaxError: Named export 'ConsoleSpanExporter' not found. The requested module '@opentelemetry/sdk-trace-base' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from '@opentelemetry/sdk-trace-base';
const { ConsoleSpanExporter, SimpleSpanProcessor } = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:189:5)

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

schneedotdev · 2023-07-07T06:38:04Z

Downgrading to version ^0.3.1 seemed to work. I'm able to run pnpm contentlayer build but the newest version (0.3.4) of contentlayer does not work for me.

savelichalex · 2023-07-07T07:46:48Z

Same issue, can confirm it

jorgemasta · 2023-07-07T08:30:42Z

It's not related to the app router but yes, I'm getting the same error.

fuma-nama · 2023-07-07T10:08:03Z

I guess that is because both Next.js and Contentlayer use open telemetry as a dependency.
Dependency conflict is likely the cause of the problem.

fuma-nama · 2023-07-07T10:34:25Z

Confirmed.
I fixed it by overriding dependency versions (using pnpm).

{
    "name": "app",
    "version": "0.1.0",
    "private": true,
    "scripts": {
        "dev": "next dev",
        "build": "next build",
        "start": "next start",
        "lint": "next lint"
    },
    "pnpm": {
        "overrides": {
            "@opentelemetry/api": "1.4.1",
            "@opentelemetry/core": "1.13.0",
            "@opentelemetry/exporter-trace-otlp-grpc": "0.39.1",
            "@opentelemetry/resources": "1.13.0",
            "@opentelemetry/sdk-trace-base": "1.13.0",
            "@opentelemetry/sdk-trace-node": "1.13.0",
            "@opentelemetry/semantic-conventions": "1.13.0"
        }
    },
    "dependencies": {
        "contentlayer": "^0.3.3",
        "next": "13.4.8",
        "next-contentlayer": "^0.3.3"
    }
}

xkrsz · 2023-07-07T10:44:09Z

@brianschnee it is not related to the App router, but rather to ESM; don't know what contentlayer has changed but the package stopped building properly when using .mjs/ESM. Using 0.3.1 works for me as well.

ParkerRex · 2023-07-07T18:28:20Z

that pnpm override -- what a great discovery. Wish I looked 3 hours ago haha.

mauriciomutte · 2023-07-08T01:33:31Z

The same for me... using 0.3.2 works as well but upgrading to 0.3.4 shows the error mentioned

contentlayerdev/contentlayer#506 (comment)

dgknca · 2023-07-08T13:57:40Z

same error

emptypockets-dev · 2023-07-08T14:54:49Z

is there a combo of versions for

contentlayer
next-contentlayer

that will work temporarily?

schneedotdev · 2023-07-08T15:58:09Z

@emptypockets-dev I'm using contentlayer: 0.3.1 and next-contentlayer: 0.3.1 for the time being. @mauriciomutte mentioned that 0.3.2 works for them as well.

abdul-hamid-achik · 2023-07-08T22:44:54Z

Confirmed. I fixed it by overriding dependency versions (using pnpm).

{
    "name": "app",
    "version": "0.1.0",
    "private": true,
    "scripts": {
        "dev": "next dev",
        "build": "next build",
        "start": "next start",
        "lint": "next lint"
    },
    "pnpm": {
        "overrides": {
            "@opentelemetry/api": "1.4.1",
            "@opentelemetry/core": "1.13.0",
            "@opentelemetry/exporter-trace-otlp-grpc": "0.39.1",
            "@opentelemetry/resources": "1.13.0",
            "@opentelemetry/sdk-trace-base": "1.13.0",
            "@opentelemetry/sdk-trace-node": "1.13.0",
            "@opentelemetry/semantic-conventions": "1.13.0"
        }
    },
    "dependencies": {
        "contentlayer": "^0.3.3",
        "next": "13.4.8",
        "next-contentlayer": "^0.3.3"
    }
}

ah mah dude, big props to you, this worked wonderfully

haxmart · 2023-07-09T11:33:51Z

Confirmed. I fixed it by overriding dependency versions (using pnpm).

{
    "name": "app",
    "version": "0.1.0",
    "private": true,
    "scripts": {
        "dev": "next dev",
        "build": "next build",
        "start": "next start",
        "lint": "next lint"
    },
    "pnpm": {
        "overrides": {
            "@opentelemetry/api": "1.4.1",
            "@opentelemetry/core": "1.13.0",
            "@opentelemetry/exporter-trace-otlp-grpc": "0.39.1",
            "@opentelemetry/resources": "1.13.0",
            "@opentelemetry/sdk-trace-base": "1.13.0",
            "@opentelemetry/sdk-trace-node": "1.13.0",
            "@opentelemetry/semantic-conventions": "1.13.0"
        }
    },
    "dependencies": {
        "contentlayer": "^0.3.3",
        "next": "13.4.8",
        "next-contentlayer": "^0.3.3"
    }
}

Amazing - thanks!

Unfortunately errors are still thrown if you have any mdxComponents in your mdx file, such as next/image. Here's what i'm facing currently:

error Error: Cannot access .propTypes on the server. You cannot dot into a client module from a server component. You can only pass the imported name through. at stringify (<anonymous>)

fuma-nama · 2023-07-09T11:59:52Z

That’s likely a bug caused by Contentlayer itself.
It doesn’t work well for App Router, try (props) => <Image {...props} />.

You can open another issue instead.

seththeskier · 2023-07-10T17:54:56Z

I'm seeing this same error after running a plain ol' npm run dev, and I don't use pnpm. Do I need to install/use pnpm to get around this?

Saadchr · 2023-07-10T20:52:24Z

I'm facing the same issue

fuma-nama · 2023-07-11T13:27:38Z

@seththeskier

I'm seeing this same error after running a plain ol' npm run dev, and I don't use pnpm. Do I need to install/use pnpm to get around this?

npm also supports overrides , my solution should be working for npm too.

I ran into the same error as contentlayerdev/contentlayer#506 (comment)

See contentlayerdev/contentlayer#506 (comment)

jorgemasta · 2023-07-12T08:22:30Z

This is the equivalent version for yarn:

    "resolutions": {
        "@opentelemetry/api": "1.4.1",
        "@opentelemetry/core": "1.13.0",
        "@opentelemetry/exporter-trace-otlp-grpc": "0.39.1",
        "@opentelemetry/resources": "1.13.0",
        "@opentelemetry/sdk-trace-base": "1.13.0",
        "@opentelemetry/sdk-trace-node": "1.13.0",
        "@opentelemetry/semantic-conventions": "1.13.0"
    }

Remember to run yarn install --force.

vinayr · 2023-08-01T13:40:59Z

For the next/image error, the workaround suggested here fixed it for me.

import NextImage, { ImageProps } from "next/image"
import { useMDXComponent } from 'next-contentlayer/hooks';

const components = {
  // Image,
  Image: (props: ImageProps) => <NextImage {...props} />,
}

interface MdxProps {
  code: string
}

export function Mdx({ code }: MdxProps) {
  const Component = useMDXComponent(code)

  return <Component components={components} />
}

thedevdavid · 2023-08-02T13:26:57Z

Not to rush anybody but there's a bunch of people in the issues, discussions, and PRs who would be happy to help. Is there any chance the Maintainers can take a look at/accept some of the help?

elie222 · 2023-08-03T13:43:39Z

Started seeing a lot of these errors today:

- error TypeError: Cannot read properties of undefined (reading 'headers')
    at eval (webpack-internal:///(rsc)/./node_modules/.pnpm/next@13.4.12_@opentelemetry+api@1.4.1_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/future/route-modules/app-route/module.js:265:61)

The fix above had originally worked for me. Not sure if this new error is related to this package.

fuma-nama · 2023-08-04T12:04:06Z

Started seeing a lot of these errors today:
- error TypeError: Cannot read properties of undefined (reading 'headers')
    at eval (webpack-internal:///(rsc)/./node_modules/.pnpm/next@13.4.12_@opentelemetry+api@1.4.1_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/future/route-modules/app-route/module.js:265:61)
The fix above had originally worked for me. Not sure if this new error is related to this package.

It is a Next.js issue that lasted for a while, see vercel/next.js#51130

jdharms · 2023-08-04T13:08:36Z

For the next/image error, the workaround suggested here fixed it for me.

import NextImage, { ImageProps } from "next/image"
import { useMDXComponent } from 'next-contentlayer/hooks';

const components = {
  // Image,
  Image: (props: ImageProps) => <NextImage {...props} />,
}

interface MdxProps {
  code: string
}

export function Mdx({ code }: MdxProps) {
  const Component = useMDXComponent(code)

  return <Component components={components} />

Been researching this for an hour or so (maybe I'm bad at Googling), this is the first workaround I've found that's worked for me.

GFGarcia · 2023-08-06T21:01:06Z

After a whole month, i'm still having the same problem:

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

My package.json:
{
"name": "blog-nextjs",
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"typecheck": "tsc --project tsconfig.json --noEmit",
"lint": "eslint src --max-warnings=0",
"test": "jest",
"test:watch": "npm test --watch",
"test:coverage": "npm test --coverage --detectOpenHandles",
"test:coverage:text": "npm test --coverageReporters='text-summary'"
},
"npm": {
"overrides": {
"@opentelemetry/api": "1.4.1",
"@opentelemetry/core": "1.13.0",
"@opentelemetry/exporter-trace-otlp-grpc": "0.39.1",
"@opentelemetry/resources": "1.13.0",
"@opentelemetry/sdk-trace-base": "1.13.0",
"@opentelemetry/sdk-trace-node": "1.13.0",
"@opentelemetry/semantic-conventions": "1.13.0"
}
},
"husky": {
"hooks": {
"pre-commit": "lint-staged"
}
},
"lint-staged": {
"src/**/*": [
"npm run lint --fix",
"npm test --findRelatedTests --bail --passWithNoTests"
]
},
"dependencies": {
"@contentlayer/core": "^0.3.4",
"@openlab/vercel-netlify-cms-github": "^1.1.1",
"@phosphor-icons/react": "^2.0.9",
"@types/node": "20.3.2",
"@types/react": "18.2.13",
"@types/react-dom": "18.2.5",
"autoprefixer": "10.4.14",
"contentlayer": "^0.3.4",
"eslint-config-next": "13.4.7",
"next": "13.4.12",
"next-compose-plugins": "^2.2.1",
"next-contentlayer": "^0.3.4",
"next-pwa": "^5.6.0",
"postcss": "8.4.24",
"react": "18.2.0",
"react-dom": "18.2.0",
"reading-time": "^1.5.0",
"rehype-autolink-headings": "^6.1.1",
"rehype-pretty-code": "^0.9.11",
"rehype-slug": "^5.1.0",
"remark-gfm": "^3.0.1",
"shiki": "^0.14.3",
"tailwindcss": "3.3.2",
"typescript": "5.0.4"
},
"devDependencies": {
"@swc/core": "^1.3.66",
"@swc/jest": "^0.2.26",
"@testing-library/jest-dom": "^5.16.5",
"@testing-library/react": "^14.0.0",
"@types/jest": "^29.5.1",
"@types/mdx": "^2.0.5",
"@types/next-pwa": "^5.6.4",
"@types/testing-library__jest-dom": "^5.14.6",
"@typescript-eslint/eslint-plugin": "^5.60.1",
"@typescript-eslint/parser": "^5.60.0",
"eslint": "8.43.0",
"eslint-config-prettier": "^8.8.0",
"eslint-plugin-import-helpers": "^1.3.1",
"eslint-plugin-prettier": "^4.2.1",
"eslint-plugin-react": "^7.32.2",
"eslint-plugin-react-hooks": "^4.6.0",
"husky": "^8.0.3",
"jest": "^29.5.0",
"jest-environment-jsdom": "^29.5.0",
"lint-staged": "^13.2.2",
"prettier": "^2.8.8",
"prettier-plugin-tailwindcss": "^0.3.0",
"tailwind-styled-components": "^2.2.0"
}
}

I use npm. Does anyone have a clue on what to do? I've already played with contentlayer and next versions but nothing worked.

emkis · 2023-08-26T23:26:26Z

I've just tested locally with next version 13.4.19 and I don't have this problem anymore. Hopefully it's solved now 🙏

thedevdavid · 2023-09-02T11:33:14Z

I've just tested locally with next version 13.4.19 and I don't have this problem anymore. Hopefully it's solved now 🙏

Not on my side. The only way to make it build for me is still:

keeping next & eslint-config-next at 13.4.9
contentlayer & next-contentlayer at 0.3.4
modify the build script "build": "contentlayer build && next build"
and add ovrrides to package.json:

"pnpm": {
    "overrides": {
      "@opentelemetry/api": "1.4.1",
      "@opentelemetry/core": "^1.15.1",
      "@opentelemetry/exporter-trace-otlp-grpc": "^0.41.1",
      "@opentelemetry/resources": "^1.15.1",
      "@opentelemetry/sdk-trace-base": "^1.15.1",
      "@opentelemetry/sdk-trace-node": "^1.15.1",
      "@opentelemetry/semantic-conventions": "^1.15.1"
    }
  }

matthewspear · 2023-09-02T12:01:15Z

I've found this issue so hard to replicate, for example with @thedevdavid's configuration above, first time I build and push to Vercel it works 🎉, I then squash some commits (force push 🙈 to tidy up this mess) and now I'm getting ❌ build errors...

TypeError: Cannot read properties of undefined (reading 'default')
--
18:55:34.588 | at getMDXComponent (file:///vercel/path0/node_modules/.pnpm/next-contentlayer@0.3.4_contentlayer@0.3.4_esbuild@0.18.10_next@13.4.9_react-dom@18.2.0_react@18.2.0/node_modules/next-contentlayer/dist/hooks/useMDXComponent.js:10:39)
... etc ...

Always builds and works locally, only when deploying to Vercel I get issues...

Seems like something to do with cached files / .contentlayer directory / the pinned dependencies versions but I'm struggling to replicate!

Am I missing anything? Anyone else in this situation?

shinchima · 2023-09-04T18:48:13Z

I've just tested locally with next version 13.4.19 and I don't have this problem anymore. Hopefully it's solved now 🙏

hey, cool, with which version of contentlayer?
Cheers

fuma-nama · 2023-09-05T09:29:50Z

The latest version, 0.3.4 works for me

shinchima · 2023-09-05T09:31:15Z

with which versions of next / next-contentlayer?

fuma-nama · 2023-09-05T10:52:19Z

Exactly the latest versions of both of them, next 13.4.19 and contentlayer 0.3.4. Not sure it's working for everyone, but at least I got it working in CodeSandbox

kriscard · 2023-09-07T00:43:07Z

I tried switching from npm to pnpm in my personal project, but I'm still encountering the next/image error even with the latest Contentlayer and NextJS 13 versions. However, it's still working fine when I use npm.

I'm hoping that this issue will be fixed soon 🙏

elie222 · 2023-10-15T12:50:05Z

Still facing this same issue with Turbo, pnpm, and Next.js 13.5.4. Been months

danisaza · 2023-10-25T03:05:14Z

I encountered this issue after upgrading next from 13.4.16 to 13.5.6.

Checking out the commit before the upgrade resolves the issue.

(I recognize that this isn't a rigorous set of steps to repro, etc - but hopefully this is helpful to anyone reading along)

For now my game plan is to pin next at 13.4.16 and wait until the issue is resolved before upgrading.

mingyeongmo · 2023-12-17T12:45:00Z

In next.js 14.0.4, I still have the same issue. I guess I'll just have to do what I suggested above.

matmac · 2024-01-02T23:29:41Z

Same problem here... Neither of the proposed changes works for me.

Using Turborepo.

When I run pnpm dev it complains about many unmet dependencies for contentlayer:

esbuild · unmet peer esbuild@"0.17.x || 0.18.x": found 0.19.11
opentelemetry · ...unmet peer @opentelemetry/api@">=1.0.0 <1.5.0": found 1.7.0 in @contentlayer/utils... (many others)
next · unmet peer next@"^12 || ^13": found 14.0.4

This is my package.json

{
  "name": "web",
  "version": "1.0.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "contentlayer build && next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "@heroicons/react": "^2.1.1",
    "@radix-ui/react-icons": "^1.3.0",
    "clsx": "^1.2.1",
    "contentlayer": "0.3.4",
    "date-fns": "^3.0.6",
    "next": "^14.0.4",
    "next-contentlayer": "0.3.4",
    "next-themes": "^0.2.1",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "react-wrap-balancer": "^1.1.0",
    "tailwind-merge": "^1.13.2",
    "ui": "workspace:*"
  },
  "devDependencies": {
    "@types/node": "^17.0.12",
    "@types/react": "^18.0.22",
    "@types/react-dom": "^18.0.7",
    "autoprefixer": "^10.4.14",
    "eslint-config-custom": "workspace:*",
    "mdast-util-toc": "^7.0.0",
    "postcss": "^8.4.24",
    "rehype-autolink-headings": "^7.1.0",
    "rehype-pretty-code": "^0.12.3",
    "rehype-slug": "^6.0.0",
    "remark": "^15.0.1",
    "remark-code-import": "^1.2.0",
    "remark-gfm": "^4.0.0",
    "shiki": "^0.14.7",
    "tailwindcss": "^3.3.2",
    "tsconfig": "workspace:*",
    "typescript": "^4.5.3"
  }
}

Any support will be much appreciated.

2-fly-4-ai · 2024-11-10T19:44:08Z

Struggled so many times with contentlayer and these opentelementary issues. Recommend anyone else running into this just learn how to build a markdown blog from scratch. This is an absolute waste of time and I would not recommend it at all.

I have used contentlayer for several years. And have it installed in many project. I often run into these terrible dependency issues that just take forever to debug. I've solved it several times but my latest nextjs14 install has the same issue again. Pulling the plug on this dependency.

It's a pity that this was not properly maintained. The contenlayer2 repo has the same issues.

fuma-nama · 2024-11-15T03:16:30Z

I would recommend content collections, its API is similar to Contentlayer and is well maintained.

omarabid · 2024-11-28T11:35:49Z

So the question is: Why does ContentLayer has open-telemetry as one of its dependencies?

schneedotdev changed the title ~~Error in node_modules when working with Next.js 13 App Router~~ Error with contentlayer 0.3.4 when working with Next.js 13 App Router Jul 7, 2023

schneedotdev changed the title ~~Error with contentlayer 0.3.4 when working with Next.js 13 App Router~~ Error when building with contentlayer 0.3.4 and Next.js 13 App Router Jul 7, 2023

wibb36 mentioned this issue Jul 7, 2023

CLI is broken #505

Closed

ParkerRex mentioned this issue Jul 7, 2023

SyntaxError when running 'pnpm dev' command in the cloned repository. contentlayerdev/next-contentlayer-example#21

Open

JosephJL added a commit to JosephJL/joseph-portfolio that referenced this issue Jul 8, 2023

added fix from github vercel build error

2be66d4

contentlayerdev/contentlayer#506 (comment)

JosephJL mentioned this issue Jul 8, 2023

Bump protobufjs, contentlayer and next-contentlayer JosephJL/joseph-portfolio#1

Merged

colinhemphill mentioned this issue Jul 8, 2023

Can't run application on fresh install colinhemphill/nextjs-resume#314

Closed

kirillkurko mentioned this issue Jul 8, 2023

Bump contentlayer from 0.3.0 to 0.3.4 kirillkurko/kkurko.dev#103

Closed

jjunior96 mentioned this issue Jul 10, 2023

Chore/fix eslint errors jjunior96/blog-next-course#53

Closed

EthanJcoding mentioned this issue Jul 11, 2023

Setting: contentlayer 세팅 EthanJcoding/Blog#63

Merged

rjmccluskey added a commit to rjmccluskey/richmccluskey.dev that referenced this issue Jul 12, 2023

Downgrade contentlayer to 0.3.1

15de444

I ran into the same error as contentlayerdev/contentlayer#506 (comment)

rjmccluskey added a commit to rjmccluskey/richmccluskey.dev that referenced this issue Jul 12, 2023

Override bad deps as workaround for contentlayer issues

c73e232

See contentlayerdev/contentlayer#506 (comment)

kirillkurko mentioned this issue Aug 7, 2023

Bump next-contentlayer from 0.3.0 to 0.3.3 kirillkurko/kkurko.dev#125

Closed

This was referenced Aug 22, 2023

Blog. yarn run dev triggers "Error: Cannot access .propTypes on the server" MemeBattle/monorepo#402

Closed

[#402] Blog: fix yarn run dev MemeBattle/monorepo#406

Closed

choubari mentioned this issue Sep 6, 2023

Seeing an Error "Cannot access .propTypes on the server" after updating to Next.js v13.4.12 shadcn-ui/taxonomy#192

Open

vagnermaltauro mentioned this issue Sep 12, 2023

Fix:#192 shadcn-ui/taxonomy#212

Open

tecchu11 mentioned this issue Oct 1, 2023

fix tecchu11/my-blog#13

Merged

tylerhoward15 mentioned this issue Oct 2, 2023

Unable to build locally chronark/chronark.com#30

Closed

This was referenced Feb 2, 2024

Update packages timlrx/contentlayer2#1

Merged

Update packages #638

Closed

Error when building with contentlayer 0.3.4 and Next.js 13 App Router #506

Error when building with contentlayer 0.3.4 and Next.js 13 App Router #506

Comments

schneedotdev commented Jul 7, 2023

When I run pnpm contentlayer build, I run into an error within node_modules and cannot resolve it.

schneedotdev commented Jul 7, 2023

savelichalex commented Jul 7, 2023

jorgemasta commented Jul 7, 2023

fuma-nama commented Jul 7, 2023

fuma-nama commented Jul 7, 2023

xkrsz commented Jul 7, 2023 • edited Loading

ParkerRex commented Jul 7, 2023

mauriciomutte commented Jul 8, 2023

dgknca commented Jul 8, 2023

emptypockets-dev commented Jul 8, 2023

schneedotdev commented Jul 8, 2023 • edited Loading

abdul-hamid-achik commented Jul 8, 2023

haxmart commented Jul 9, 2023

fuma-nama commented Jul 9, 2023 • edited Loading

seththeskier commented Jul 10, 2023

Saadchr commented Jul 10, 2023

fuma-nama commented Jul 11, 2023

jorgemasta commented Jul 12, 2023

vinayr commented Aug 1, 2023 • edited Loading

thedevdavid commented Aug 2, 2023

elie222 commented Aug 3, 2023

fuma-nama commented Aug 4, 2023 • edited Loading

jdharms commented Aug 4, 2023

GFGarcia commented Aug 6, 2023

emkis commented Aug 26, 2023

thedevdavid commented Sep 2, 2023

matthewspear commented Sep 2, 2023

shinchima commented Sep 4, 2023

fuma-nama commented Sep 5, 2023

shinchima commented Sep 5, 2023

fuma-nama commented Sep 5, 2023

kriscard commented Sep 7, 2023

elie222 commented Oct 15, 2023 • edited Loading

danisaza commented Oct 25, 2023

mingyeongmo commented Dec 17, 2023

matmac commented Jan 2, 2024

2-fly-4-ai commented Nov 10, 2024

fuma-nama commented Nov 15, 2024 • edited Loading

omarabid commented Nov 28, 2024

When I run `pnpm contentlayer build`, I run into an error within node_modules and cannot resolve it.

xkrsz commented Jul 7, 2023 •

edited

Loading

schneedotdev commented Jul 8, 2023 •

edited

Loading

fuma-nama commented Jul 9, 2023 •

edited

Loading

vinayr commented Aug 1, 2023 •

edited

Loading

fuma-nama commented Aug 4, 2023 •

edited

Loading

elie222 commented Oct 15, 2023 •

edited

Loading

fuma-nama commented Nov 15, 2024 •

edited

Loading