Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(graphql) generate:schema fails on windows due to url protocol c: #9309

Open
6TELOIV opened this issue Nov 18, 2024 · 0 comments · May be fixed by #9311
Open

(graphql) generate:schema fails on windows due to url protocol c: #9309

6TELOIV opened this issue Nov 18, 2024 · 0 comments · May be fixed by #9311
Assignees

Comments

@6TELOIV
Copy link

6TELOIV commented Nov 18, 2024

Describe the Bug

Generating a graphql schema on windows with payload-graphql generate:schema fails with:
Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'

Link to the code that reproduces this issue

https://github.com/6TELOIV/graphql-schema-windows-url-scheme

Reproduction Steps

This error ONLY effects windows, and is due to c: being confused for a URL scheme (i.e http:, file:, or node:)

  1. Clone the repro repo
  2. Run pnpm i (or your favorite pacman)
  3. Run pnpm payload-graphql generate:schema (or your favorite pacman)
  4. Observe the error

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

area: core

Environment Info

Payload: 3.0.0-beta.134
Next: 15.0.0
Node: 2.11.0
@6TELOIV 6TELOIV added status: needs-triage Possible bug which hasn't been reproduced yet v3 validate-reproduction labels Nov 18, 2024
@denolfe denolfe removed the v3 label Nov 19, 2024
@github-actions github-actions bot removed the status: needs-triage Possible bug which hasn't been reproduced yet label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants