Can't build payload

[ben-biber]

Describe the Bug

Can't build payload even with the starter template

Link to the code that reproduces this issue

default repo

Reproduction Steps

• npx create-payload-app
• use website template
• run npm build

   ▲ Next.js 15.0.3
   - Environments: .env
   - Experiments (use with caution):
     · turbo

   Creating an optimized production build ...
Failed to compile.

./src/endpoints/seed/index.ts + 8 modules
Unexpected end of JSON input

./node_modules/@payloadcms/richtext-lexical/dist/exports/client/index.js + 9 modules
Unexpected end of JSON input

./node_modules/@payloadcms/ui/dist/exports/client/index.js + 16 modules
Unexpected end of JSON input

./node_modules/@payloadcms/ui/dist/exports/shared/index.js + 20 modules
Unexpected end of JSON input

./node_modules/@radix-ui/react-select/dist/index.mjs + 42 modules
Unexpected end of JSON input


> Build failed because of webpack errors

Which area(s) are affected? (Select all that apply)

Not sure

Environment Info

Binaries:
  Node: 23.3.0
  npm: 10.9.0
  Yarn: 1.22.22
  pnpm: 9.14.2
Relevant Packages:
  payload: 3.1.1
  next: 15.0.3
  @payloadcms/email-nodemailer: 3.1.1
  @payloadcms/graphql: 3.1.1
  @payloadcms/live-preview: 3.1.1
  @payloadcms/live-preview-react: 3.1.1
  @payloadcms/next/utilities: 3.1.1
  @payloadcms/payload-cloud: 3.1.1
  @payloadcms/plugin-form-builder: 3.1.1
  @payloadcms/plugin-nested-docs: 3.1.1
  @payloadcms/plugin-redirects: 3.1.1
  @payloadcms/plugin-search: 3.1.1
  @payloadcms/plugin-seo: 3.1.1
  @payloadcms/richtext-lexical: 3.1.1
  @payloadcms/translations: 3.1.1
  @payloadcms/ui/shared: 3.1.1
  react: 19.0.0-rc-65a56d0e-20241020
  react-dom: 19.0.0-rc-65a56d0e-20241020
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:15 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@beta -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload

[energee]

Seeing this, too

[AlessioGr]

I cannot reproduce this on a fresh website template and Node 23.3.0. Will need a reproduction to look into it

[AlessioGr]

nodejs/node#55826

Looks like this might be a bug in some node v23 versions. Does this work on node v22?

[energee]

Yes, v22 is fine

[udany]

Well... color me screwed...

I have to use v23 otherwise this doesn't work, but I can't build it on v23...