Can't start server on clean install

[dbsmck]

Describe the Bug

App won't open/run in new installation

Link to the code that reproduces this issue

pnpm dev

Reproduction Steps

Create new environment, running node 22 (or 20).

npx create-payload-app

tried both postgres and sqlite

install successful, cd into directory

pnpm dev

starts. load localhost:3000

Attempted import error: 'WebStreamReader' is not exported from 'peek-readable' (imported as 'WebStreamReader').

Import trace for requested module:
./node_modules/.pnpm/[email protected]/node_modules/strtok3/lib/core.js
./node_modules/.pnpm/[email protected]/node_modules/file-type/core.js
./node_modules/.pnpm/[email protected]/node_modules/file-type/index.js
./node_modules/.pnpm/[email protected][email protected][email protected][email protected][email protected][email protected][email protected]/node_modules/payload/dist/uploads/getFileByPath.js
./node_modules/.pnpm/[email protected][email protected][email protected][email protected][email protected][email protected][email protected]/node_modules/payload/dist/index.js
./src/app/(frontend)/page.tsx
 ⨯ ./node_modules/.pnpm/[email protected]/node_modules/strtok3/lib/core.js
Attempted import error: 'WebStreamReader' is not exported from 'peek-readable' (imported as 'WebStreamReader').

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

area: core, area: ui

Environment Info

nodejs 22 or 20 / nextjs 15
mac os x
pnpm installed with brew

cant run pnpm payload info:
training/work/node_modules/.pnpm/[email protected]/node_modules/strtok3/lib/core.js?tsx-namespace=1738158941192:1
import { StreamReader, WebStreamReader } from 'peek-readable';
                       ^^^^^^^^^^^^^^^
SyntaxError: The requested module 'peek-readable' does not provide an export named 'WebStreamReader'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:180:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:263:5)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:547:26)
    at async start (XZY/projects/training/work/node_modules/.pnpm/[email protected][email protected][email protected][email protected][email protected][email protected][email protected]/node_modules/payload/bin.js:29:23)

[github-actions[bot]]

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

[renansantos]

Same here!

[dbsmck]

Tried 3.19 and 3.18 versions and both have same issue

[makara4code]

Same issue here.

[khnn]

Same here with:
node 20.17, pnpm 9.10

[RuanGomsSG]

Same here

[kedimuzafer]

Yes this is also my problem, after trying tons of things for hours that is not related with payload cms, I am here too. Please fix this

[fofoy]

For anyone encountering this issue, you just need to pin peek-readable dependency to 5.3.1 for now until the dependency author fixes the issue, you can follow the status here : Borewit/peek-readable#791 (comment)

[makara4code]

For anyone encountering this issue, you just need to pin peek-readable dependency to 5.3.1 for now until the dependency author fixes the issue, you can follow the status here : Borewit/peek-readable#791 (comment)

It's working

[jasperdegens]

For anyone encountering this issue, you just need to pin peek-readable dependency to 5.3.1 for now until the dependency author fixes the issue, you can follow the status here : Borewit/peek-readable#791 (comment)

Can confirm this works for me. Depending on your repo structure, you can also set "overrides" in your package.json:

"overrides": { "peek-readable": "5.3.1" }

[AlessioGr]

This has been fixed in version 5.4.2 of peek-readable. As a result, this issue will no longer occur in fresh installs. If it's still broken for you, you have 2 options:

Perform a clean install (recommended)

Your package manager should automatically install the latest peek-readable version, unless the older, broken version is still cached or pinned in your lockfile. Simply prune the cache, delete the lockfile and delete the node_modules folder, then install again.

If you're using pnpm (our recommended package manager), you can run this command:

pnpm store prune && rm -rf node_modules pnpm-lock.yaml && pnpm i

Please delete both node_modules and the lockfile, as package managers behave incorrectly if only one of them is deleted.

Pin the version of peek-readable

You can pin the version of peek-readable in your package.json - see the comment from @jasperdegens: #10900 (comment)