Dev Server crashing

[siyabendoezdemir]

╥
╠══╦══╗
║ ║ ║
║ ║ ╠─An interrupt was produced by #39.
║ ║ ║
║ ║ ▼
║ ║
║ ╠─An unchecked error was produced.
║ ║
║ ║ TypeError: Cannot read properties of undefined (reading 'tracer')
║ ║ at f (file:///Users/siyabendoezdemir/Desktop/Projects/tweet-ai/node_modules/@effect-ts/system/_src/Effect/derive.ts:88:76)
║ ║ at IRead.f (file:///Users/siyabendoezdemir/Desktop/Projects/tweet-ai/node_modules/@effect-ts/system/_src/Effect/has.ts:113:33)
║ ║ at FiberContext.evaluateNow (file:///Users/siyabendoezdemir/Desktop/Projects/tweet-ai/node_modules/@effect-ts/system/_src/Fiber/context.ts:1136:31)
║ ║ at file:///Users/siyabendoezdemir/Desktop/Projects/tweet-ai/node_modules/@effect-ts/system/_src/Fiber/context.ts:576:33
║ ║ at file:///Users/siyabendoezdemir/Desktop/Projects/tweet-ai/node_modules/@effect-ts/system/_src/Support/Scheduler/index.ts:15:9
║ ║
║ ║ Fiber: #41 (started at: 2024-05-19T00:10:59.162Z) was supposed to continue to:
║ ║
║ ║ Fiber: #41 (started at: 2024-05-19T00:10:59.162Z) Execution trace:
║ ║
║ ║ Fiber: #41 (started at: 2024-05-19T00:10:59.162Z) was spawned by:
║ ║
║ ║ Fiber: #39 (started at: 2024-05-19T00:10:59.162Z) was supposed to continue to:
║ ║
║ ║ Fiber: #39 (started at: 2024-05-19T00:10:59.162Z) Execution trace:
║ ║
║ ║ Fiber: #39 (started at: 2024-05-19T00:10:59.162Z) was spawned by:
║ ║
║ ║ Fiber: #37 (started at: 2024-05-19T00:10:59.161Z) was supposed to continue to:
║ ║
║ ║ Fiber: #37 (started at: 2024-05-19T00:10:59.161Z) Execution trace:
║ ║
║ ║ Fiber: #37 (started at: 2024-05-19T00:10:59.161Z) was spawned by:
║ ║
║ ║ Fiber: #26 (started at: 2024-05-19T00:10:59.158Z) was supposed to continue to:
║ ║
║ ║ Fiber: #26 (started at: 2024-05-19T00:10:59.158Z) Execution trace:
║ ║
║ ║ Fiber: #26 (started at: 2024-05-19T00:10:59.158Z) was spawned by:
║ ║
║ ║ Fiber: #5 (started at: 2024-05-19T00:10:58.809Z) was supposed to continue to:
║ ║
║ ║ Fiber: #5 (started at: 2024-05-19T00:10:58.809Z) Execution trace:
║ ║
║ ║ Fiber: #5 (started at: 2024-05-19T00:10:58.809Z) was spawned by:
║ ║
║ ║ Fiber: #0 (started at: 2024-05-19T00:10:58.800Z) was supposed to continue to:
║ ║
║ ║ Fiber: #0 (started at: 2024-05-19T00:10:58.800Z) Execution trace:
║ ║
║ ║ Fiber: #0 (started at: 2024-05-19T00:10:58.800Z) was spawned by:
║ ▼
▼

OS: darwin 23.1.0 (arch: arm64)
Process: /opt/homebrew/Cellar/node/21.6.1/bin/node /Users/siyabendoezdemir/Desktop/Projects/tweet-ai/node_modules/next/dist/server/lib/start-server.js
Node version: v21.6.1
Contentlayer version: 0.3.4

[dtechoracle]

I am currently having the same issues. Have you fixed yours?

[Virous77]

@siyabendoezdemir are you using nextjs?

[dtechoracle]

Yes, I am

…

On Thu, Jun 13, 2024, 7:20 PM Reetesh Kumar ***@***.***> wrote: @siyabendoezdemir <https://github.com/siyabendoezdemir> are you using nextjs? — Reply to this email directly, view it on GitHub <#659 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQPDNXGDNL7W6RW4SJEUUGTZHHPIRAVCNFSM6AAAAABH53O3U2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRWGQ4TQMBZGA> . You are receiving this because you commented.Message ID: ***@***.***>

[Virous77]

@dtechoracle for me it's working well here with Next.JS latest version. You can check the repo and version here.

https://github.com/Virous77/Reetesh/tree/main/frontend

[ndom91]

Running into this too with the following relevant dependencies. I'm using the notion contentlayer data source and fumadocs as a next.js 14 based docs framework (Nextra fork sort of)

"dependencies": {
  "@notionhq/client": "^2.2.15",
  "contentlayer": "^0.3.4",
  "contentlayer-source-notion": "0.0.1-alpha.26",
  "fumadocs-contentlayer": "^1.1.34",
  "fumadocs-core": "12.2.4",
  "fumadocs-mdx": "8.2.33",
  "fumadocs-ui": "12.2.4",
  "next": "^14.2.4",
  "next-contentlayer": "^0.3.4",
  "react": "^18.3.1",
  "react-dom": "^18.3.1"
},

[stale]

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.

[matheuseabra]

I'm also having the exact same problem, any ideas to fix?

[Virous77]

@matheuseabra are you using Next.JS latest version?