-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Conversation
🦋 Changeset detectedLatest commit: 857e108 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this 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?
The check would work — |
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>
There was a problem hiding this 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
closes #7976
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpm changeset
and following the prompts. All changesets should bepatch
until SvelteKit 1.0