Skip to content

next-contentlayer 0.3.3 breaks notion source #483

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gty3 opened this issue Jun 8, 2023 · 1 comment
Closed

next-contentlayer 0.3.3 breaks notion source #483

gty3 opened this issue Jun 8, 2023 · 1 comment

Comments

@gty3
Copy link

gty3 commented Jun 8, 2023

I created a new Next.js 13.4 project with ContentLayer using Notion as a source. Just added contentlayer.config.ts and the build fails. If I use contentlayer-next 0.3.3 I get the following error. If I use contentlayer-next 0.3.2, no error. https://github.com/gty3/kani/blob/main/contentlayer.config.ts

`This error shouldn't have happened. Please consider opening a GitHub issue with the stack trace below here:
https://github.com/contentlayerdev/contentlayer/issues


╠══╦══╗
║ ║ ║
║ ║ ╠─An interrupt was produced by #39.
║ ║ ║
║ ║ ▼
║ ║
║ ╠─An unchecked error was produced.
║ ║
║ ║ TypeError: Cannot read properties of undefined (reading 'tracer')
║ ║ at f (file:///home/gty/Documents/kani/node_modules/.pnpm/@Effect-TS[email protected]/node_modules/@effect-ts/system/_src/Effect/derive.ts:88:76)
║ ║ at IRead.f (file:///home/gty/Documents/kani/node_modules/.pnpm/@Effect-TS[email protected]/node_modules/@effect-ts/system/_src/Effect/has.ts:113:33)
║ ║ at FiberContext.evaluateNow (file:///home/gty/Documents/kani/node_modules/.pnpm/@Effect-TS[email protected]/node_modules/@effect-ts/system/_src/Fiber/context.ts:1136:31)
║ ║ at file:///home/gty/Documents/kani/node_modules/.pnpm/@Effect-TS[email protected]/node_modules/@effect-ts/system/_src/Fiber/context.ts:576:33
║ ║ at file:///home/gty/Documents/kani/node_modules/.pnpm/@Effect-TS[email protected]/node_modules/@effect-ts/system/_src/Support/Scheduler/index.ts:15:9
║ ║
║ ║ Fiber: #41 (started at: 2023-06-08T02:01:39.711Z) was supposed to continue to:
║ ║
║ ║ Fiber: #41 (started at: 2023-06-08T02:01:39.711Z) Execution trace:
║ ║
║ ║ Fiber: #41 (started at: 2023-06-08T02:01:39.711Z) was spawned by:
║ ║
║ ║ Fiber: #39 (started at: 2023-06-08T02:01:39.711Z) was supposed to continue to:
║ ║
║ ║ Fiber: #39 (started at: 2023-06-08T02:01:39.711Z) Execution trace:
║ ║
║ ║ Fiber: #39 (started at: 2023-06-08T02:01:39.711Z) was spawned by:
║ ║
║ ║ Fiber: #37 (started at: 2023-06-08T02:01:39.710Z) was supposed to continue to:
║ ║
║ ║ Fiber: #37 (started at: 2023-06-08T02:01:39.710Z) Execution trace:
║ ║
║ ║ Fiber: #37 (started at: 2023-06-08T02:01:39.710Z) was spawned by:
║ ║
║ ║ Fiber: #26 (started at: 2023-06-08T02:01:39.703Z) was supposed to continue to:
║ ║
║ ║ Fiber: #26 (started at: 2023-06-08T02:01:39.703Z) Execution trace:
║ ║
║ ║ Fiber: #26 (started at: 2023-06-08T02:01:39.703Z) was spawned by:
║ ║
║ ║ Fiber: #5 (started at: 2023-06-08T02:01:39.337Z) was supposed to continue to:
║ ║
║ ║ Fiber: #5 (started at: 2023-06-08T02:01:39.337Z) Execution trace:
║ ║
║ ║ Fiber: #5 (started at: 2023-06-08T02:01:39.337Z) was spawned by:
║ ║
║ ║ Fiber: #0 (started at: 2023-06-08T02:01:39.321Z) was supposed to continue to:
║ ║
║ ║ Fiber: #0 (started at: 2023-06-08T02:01:39.321Z) Execution trace:
║ ║
║ ║ Fiber: #0 (started at: 2023-06-08T02:01:39.321Z) was spawned by:
║ ▼

OS: linux 5.15.0-73-generic (arch: x64)
Process: /home/gty/.nvm/versions/node/v18.5.0/bin/node /home/gty/Documents/kani/node_modules/.pnpm/next@13.4.4_@opentelemetry[email protected][email protected][email protected]/node_modules/next/dist/compiled/jest-worker/processChild.js
Node version: v18.5.0
Contentlayer version: 0.3.3
`

@stale
Copy link

stale bot commented Aug 7, 2023

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.

@stale stale bot added the meta: stale label Aug 7, 2023
@stale stale bot closed this as completed Aug 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant