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

error in dev mode if global fetch is used with relative URL #8370

Merged
merged 3 commits into from
Jan 9, 2023

Conversation

Rich-Harris
Copy link
Member

closes #7976

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

  • If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0
@changeset-bot
Copy link

changeset-bot bot commented Jan 6, 2023

🦋 Changeset detected

Latest commit: 857e108

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@sveltejs/kit Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel
Copy link

vercel bot commented Jan 7, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
kit 🔄 Building (Inspect) Jan 7, 2023 at 6:39PM (UTC)
Copy link
Member

@Conduitry Conduitry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens if someone uses a protocol-relative URL like //foo/bar? This check would fail to catch it and it would (I think) then still fail with the global fetch.

Can we instead just check something simpler like that the URL matches /^\w+:\/\//? Or heck, just hard code http:// and https:// since I don't think anything else would succeed anyway?

@Rich-Harris
Copy link
Member Author

The check would work — new URL('//foo.com', 'fake://fake').protocol === 'fake:'. But yeah, a regex is probably simpler. I opened a suggestion

@Conduitry
Copy link
Member

Oh, whoops, not sure what I was thinking there anymore. I do still like the regex though.

Co-authored-by: Rich Harris <richard.a.harris@gmail.com>
Copy link
Member

@dummdidumm dummdidumm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving the regex approach. Hardcoding http(s) would make things like tauri apps etc impossible to use the global fetch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants