~M•29
Published on

Issue 02 - Unchecked Error

Authors
  • avatar
    Name
    MDolce
    Twitter
Table of Contents

Error we need to solve:


Contentlayer config change detected. Updating type definitions and data...
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 #1829.
║  ║  ║
║  ║  ▼
║  ║
║  ╠─An unchecked error was produced.
║  ║
║  ║ TypeError: fieldDef.of.def is not a function
║  ║     at fieldDefEntryToCoreFieldDef (file:///Users/mrsdo/2024/29signals.com/03-DEVELOPMENT/dev-m29-202401181040-vercel/-m-29-20241181040-01-uiux/node_modules/@shipixen/source-files/src/schema/provideSchema.ts:214:39)
║  ║     at file:///Users/mrsdo/2024/29signals.com/03-DEVELOPMENT/dev-m29-202401181040-vercel/-m-29-20241181040-01-uiux/node_modules/@shipixen/source-files/src/schema/provideSchema.ts:26:9
║  ║     at Array.map (<anonymous>)
║  ║     at next (file:///Users/mrsdo/2024/29signals.com/03-DEVELOPMENT/dev-m29-202401181040-vercel/-m-29-20241181040-01-uiux/node_modules/@shipixen/source-files/src/schema/provideSchema.ts:25:70)
║  ║     at Generator.next (<anonymous>)
║  ║     at ISuspend.factory (file:///Users/mrsdo/2024/29signals.com/03-DEVELOPMENT/dev-m29-202401181040-vercel/-m-29-20241181040-01-uiux/node_modules/@effect-ts/system/_src/Effect/gen.ts:135:28)
║  ║     at FiberContext.evaluateNow (file:///Users/mrsdo/2024/29signals.com/03-DEVELOPMENT/dev-m29-202401181040-vercel/-m-29-20241181040-01-uiux/node_modules/@effect-ts/system/_src/Fiber/context.ts:1173:51)
║  ║     at file:///Users/mrsdo/2024/29signals.com/03-DEVELOPMENT/dev-m29-202401181040-vercel/-m-29-20241181040-01-uiux/node_modules/@effect-ts/system/_src/Fiber/context.ts:576:33
║  ║     at file:///Users/mrsdo/2024/29signals.com/03-DEVELOPMENT/dev-m29-202401181040-vercel/-m-29-20241181040-01-uiux/node_modules/@effect-ts/system/_src/Support/Scheduler/index.ts:15:9
║  ║
║  ║ Fiber: #1831 (started at: 2024-01-19T13:34:40.443Z) was supposed to continue to: <empty trace>
║  ║
║  ║ Fiber: #1831 (started at: 2024-01-19T13:34:40.443Z) Execution trace: <empty trace>
║  ║
║  ║ Fiber: #1831 (started at: 2024-01-19T13:34:40.443Z) was spawned by:
║  ║
║  ║ Fiber: #1829 (started at: 2024-01-19T13:34:40.443Z) was supposed to continue to: <empty trace>
║  ║
║  ║ Fiber: #1829 (started at: 2024-01-19T13:34:40.443Z) Execution trace: <empty trace>
║  ║
║  ║ Fiber: #1829 (started at: 2024-01-19T13:34:40.443Z) was spawned by:
║  ║
║  ║ Fiber: #1827 (started at: 2024-01-19T13:34:40.442Z) was supposed to continue to: <empty trace>
║  ║
║  ║ Fiber: #1827 (started at: 2024-01-19T13:34:40.442Z) Execution trace: <empty trace>
║  ║
║  ║ Fiber: #1827 (started at: 2024-01-19T13:34:40.442Z) was spawned by:
║  ║
║  ║ Fiber: #1821 (started at: 2024-01-19T13:34:40.431Z) was supposed to continue to: <empty trace>
║  ║
║  ║ Fiber: #1821 (started at: 2024-01-19T13:34:40.431Z) Execution trace: <empty trace>
║  ║
║  ║ Fiber: #1821 (started at: 2024-01-19T13:34:40.431Z) was spawned by:
║  ║
║  ║ Fiber: #5 (started at: 2024-01-19T12:57:18.411Z) was supposed to continue to: <empty trace>
║  ║
║  ║ Fiber: #5 (started at: 2024-01-19T12:57:18.411Z) Execution trace: <empty trace>
║  ║
║  ║ Fiber: #5 (started at: 2024-01-19T12:57:18.411Z) was spawned by:
║  ║
║  ║ Fiber: #0 (started at: 2024-01-19T12:57:18.346Z) was supposed to continue to: <empty trace>
║  ║
║  ║ Fiber: #0 (started at: 2024-01-19T12:57:18.346Z) Execution trace: <empty trace>
║  ║
║  ║ Fiber: #0 (started at: 2024-01-19T12:57:18.346Z) was spawned by: <empty trace>
║  ▼

OS: darwin 22.6.0 (arch: x64)
Process: /Users/mrsdo/.nvm/versions/node/v20.10.0/bin/node /Users/mrsdo/2024/29signals.com/03-DEVELOPMENT/dev-m29-202401181040-vercel/-m-29-20241181040-01-uiux/node_modules/next/dist/server/lib/start-server.js
Node version: v20.10.0
Contentlayer version: 1.0.2

Process finished with exit code 0

Assumptions:

  1. Error happened around the time a new field type to the Blog Doc Type in contentlayer.config.js
  2. Process exited automatically after the error
  3. Process restarted manually with no known issues

Solution?

TBD

REF(s):

TBD