cross-env.js MODULE_NOT_FOUND

[NeilRiver]

Describe the Bug

pnpm dev                                                                                                                                                                            

> hoster-site@1.0.0 dev C:\Users\user\Desktop\hoster-site
> cross-env NODE_OPTIONS=--no-deprecation next dev

node:internal/modules/cjs/loader:1252
  throw err;
  ^

Error: Cannot find module 'C:\Users\user\Desktop\hoster-site\node_modules\cross-env\src\bin\cross-env.js'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1249:15)
    at Function._load (node:internal/modules/cjs/loader:1075:27)
    at TracingChannel.traceSync (node:diagnostics_channel:315:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:218:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)
    at node:internal/main/run_main_module:36:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v22.11.0
 ELIFECYCLE  Command failed with exit code 1.
PS C:\Users\user\Desktop\hoster-site> 

it can be cured if you install cross-env.js yourself again
npm i cross-env

Link to the code that reproduces this issue

///

Reproduction Steps

1. npx create-payload-app
2. pnpm dev

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

area: core, db-postgres

Environment Info

pnpm payload info

> hoster-site@1.0.0 payload C:\Users\user\Desktop\hoster-site
> cross-env NODE_OPTIONS=--no-deprecation payload "info"

node:internal/modules/cjs/loader:1252
  throw err;
  ^

Error: Cannot find module 'C:\Users\user\Desktop\hoster-site\node_modules\cross-env\src\bin\cross-env.js'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1249:15)
    at Function._load (node:internal/modules/cjs/loader:1075:27)
    at TracingChannel.traceSync (node:diagnostics_channel:315:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:218:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)
    at node:internal/main/run_main_module:36:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v22.11.0
 ELIFECYCLE  Command failed with exit code 1.
PS C:\Users\user\Desktop\hoster-site>

[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

[AlessioGr]

Hi, I have converted this into a discussion as I cannot reproduce it and believe this is likely an issue on your end. It would help if you could share more information, e.g. screenshot of the output from create-payload-app. Are you getting any error messages during installation? Is the issue resolved if you manually run pnpm i?

[SublimeProphets]

@AlessioGr I did experienced the same bug today with the exact behavior as mentioned abhove, however i could truly solve it by only running pnpm i.