Fields of type 'list' break everything but 'json' and 'string' work

I’m busy trying to implement Contentlayers on a site with a lot of mdx files as the content for a blog. When I use the type: 'list' property in a field everything breaks.

`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 #16. ║ ║ ║ ║ ║ ▼ ║ ║ ║ ╠─An unchecked error was produced. ║ ║ ║ ║ TypeError: Cannot read properties of undefined (reading ‘type’) ║ ║ at fieldListItemsToCoreFieldListDefItems (file:///workspace/avif.io/node_modules/@contentlayer/source-files/src/schema/provideSchema.ts:251:28) ║ ║ at fieldDefEntryToCoreFieldDef (file:///workspace/avif.io/node_modules/@contentlayer/source-files/src/schema/provideSchema.ts:159:13) ║ ║ at file:///workspace/avif.io/node_modules/@contentlayer/source-files/src/schema/provideSchema.ts:26:9 ║ ║ at Array.map (<anonymous>) ║ ║ at next (file:///workspace/avif.io/node_modules/@contentlayer/source-files/src/schema/provideSchema.ts:25:64) ║ ║ at Generator.next (<anonymous>) ║ ║ at ISuspend.factory (file:///workspace/avif.io/node_modules/@effect-ts/system/_src/Effect/gen.ts:135:28) ║ ║ at FiberContext.evaluateNow (file:///workspace/avif.io/node_modules/@effect-ts/system/_src/Fiber/context.ts:1173:51) ║ ║ at file:///workspace/avif.io/node_modules/@effect-ts/system/_src/Fiber/context.ts:576:33 ║ ║ at file:///workspace/avif.io/node_modules/@effect-ts/system/_src/Support/Scheduler/index.ts:15:9 ║ ║ ║ ║ Fiber: #18 (started at: 2022-04-24T14:08:00.132Z) was supposed to continue to: ║ ║ ║ ║ a future continuation at packages/@contentlayer/source-files/src/index.ts:104:19 ║ ║ ║ ║ Fiber: #18 (started at: 2022-04-24T14:08:00.132Z) Execution trace: ║ ║ ║ ║ packages/@contentlayer/source-files/src/schema/provideSchema.ts:18:8 ║ ║ ║ ║ Fiber: #18 (started at: 2022-04-24T14:08:00.132Z) was spawned by: ║ ║ ║ ║ Fiber: #16 (started at: 2022-04-24T14:08:00.132Z) was supposed to continue to: ║ ║ ║ ║ a future continuation at packages/@contentlayer/core/src/generation/generate-dotpkg.ts:82:13 ║ ║ ║ ║ Fiber: #16 (started at: 2022-04-24T14:08:00.132Z) Execution trace: ║ ║ ║ ║ packages/@contentlayer/core/src/generation/generate-dotpkg.ts:78:16 ║ ║ ║ ║ Fiber: #16 (started at: 2022-04-24T14:08:00.132Z) was spawned by: ║ ║ ║ ║ Fiber: #14 (started at: 2022-04-24T14:08:00.129Z) was supposed to continue to: <empty trace> ║ ║ ║ ║ Fiber: #14 (started at: 2022-04-24T14:08:00.129Z) Execution trace: <empty trace> ║ ║ ║ ║ Fiber: #14 (started at: 2022-04-24T14:08:00.129Z) was spawned by: ║ ║ ║ ║ Fiber: #10 (started at: 2022-04-24T14:08:00.128Z) was supposed to continue to: <empty trace> ║ ║ ║ ║ Fiber: #10 (started at: 2022-04-24T14:08:00.128Z) Execution trace: <empty trace> ║ ║ ║ ║ Fiber: #10 (started at: 2022-04-24T14:08:00.128Z) was spawned by: ║ ║ ║ ║ Fiber: #3 (started at: 2022-04-24T14:07:59.958Z) was supposed to continue to: <empty trace> ║ ║ ║ ║ Fiber: #3 (started at: 2022-04-24T14:07:59.958Z) Execution trace: ║ ║ ║ ║ packages/next-contentlayer/src/plugin.ts:17:94 ║ ║ packages/@contentlayer/utils/src/effect/Stream.ts:32:83 ║ ║ packages/@contentlayer/core/src/getConfig/index.ts:192:13 ║ ║ packages/@contentlayer/core/src/getConfig/index.ts:181:28 ║ ║ packages/@contentlayer/core/src/getConfig/index.ts:179:44 ║ ║ packages/@contentlayer/core/src/getConfig/index.ts:166:28 ║ ║ packages/@contentlayer/core/src/getConfig/index.ts:164:31 ║ ║ packages/@contentlayer/core/src/getConfig/index.ts:151:28 ║ ║ packages/@contentlayer/core/src/getConfig/index.ts:149:15 ║ ║ packages/@contentlayer/core/src/getConfig/index.ts:146:15 ║ ║ packages/@contentlayer/core/src/getConfig/index.ts:145:15 ║ ║ packages/@contentlayer/core/src/cwd.ts:24:43 ║ ║ packages/@contentlayer/core/src/getConfig/index.ts:134:27 ║ ║ packages/@contentlayer/core/src/getConfig/index.ts:121:10 ║ ║ packages/@contentlayer/core/src/getConfig/esbuild.ts:118:12 ║ ║ packages/@contentlayer/core/src/getConfig/esbuild.ts:121:14 ║ ║ packages/@contentlayer/core/src/getConfig/esbuild.ts:70:15 ║ ║ packages/@contentlayer/core/src/getConfig/esbuild.ts:69:10 ║ ║ packages/@contentlayer/core/src/getConfig/esbuild.ts:68:10 ║ ║ packages/@contentlayer/core/src/getConfig/esbuild.ts:51:22 ║ ║ packages/@contentlayer/core/src/getConfig/esbuild.ts:76:10 ║ ║ packages/@contentlayer/core/src/getConfig/esbuild.ts:75:12 ║ ║ packages/@contentlayer/core/src/getConfig/esbuild.ts:75:46 ║ ║ packages/@contentlayer/core/src/getConfig/esbuild.ts:89:20 ║ ║ packages/@contentlayer/core/src/getConfig/esbuild.ts:88:12 ║ ║ ║ ║ Fiber: #3 (started at: 2022-04-24T14:07:59.958Z) was spawned by: ║ ║ ║ ║ Fiber: #0 (started at: 2022-04-24T14:07:59.943Z) was supposed to continue to: <empty trace> ║ ║ ║ ║ Fiber: #0 (started at: 2022-04-24T14:07:59.943Z) Execution trace: ║ ║ ║ ║ packages/@contentlayer/utils/src/tracing-effect/index.ts:45:45 ║ ║ packages/@contentlayer/core/src/cwd.ts:22:49 ║ ║ packages/@contentlayer/core/src/cwd.ts:9:18 ║ ║ packages/@contentlayer/core/src/cwd.ts:8:23 ║ ║ packages/@contentlayer/core/src/cwd.ts:7:29 ║ ║ packages/@contentlayer/core/src/runMain.ts:23:32 ║ ║ packages/@contentlayer/core/src/runMain.ts:14:12 ║ ║ ║ ║ Fiber: #0 (started at: 2022-04-24T14:07:59.943Z) was spawned by: <empty trace> ║ ▼ ▼

OS: linux 5.16.20-051620-generic (arch: x64) Process: /home/gitpod/.nvm/versions/node/v16.14.2/bin/node /workspace/avif.io/node_modules/.bin/next dev Node version: v16.14.2 Contentlayer version: 0.2.4`

[schickling]

Sorry about the confusion in case you ran into a problem like described above. This isn’t technically a problem with Contentlayer itself but rather occurs when “wrongly using it”. (Thanks @sidwebworks for pointing out the solution to the described problem.)

In order to improve the DX for future users running into a similar situation, I’m planning to implement Runtime config / schema validation functionality (see #214).

[sidwebworks]

You need to add the of property in the field

of: {
  type: 'string',
},