-
-
Notifications
You must be signed in to change notification settings - Fork 2k
[fix] allow SvelteKit to be used without bundling #7950
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
Conversation
🦋 Changeset detectedLatest commit: 147c0e1 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 |
this is neat! can we rely on |
using |
Yes. If they weren't then the code currently in |
Co-authored-by: Geoff Rich <4992896+geoffrich@users.noreply.github.com>
We still have |
Thanks! I wasn't aware of |
Banish
import.meta.env
from our codebase so that@sveltejs/kit
works without bundlingFixes vitest-dev/vitest#2298 and a ton of other issues I've seen like this around the ecosystem
We should probably print a big loud warning when running
svelte-package
if anyone tries to useimport { browser, dev } from '$app/environment'
and tell them to useesm-env
unless they intend for their package to only be used in SvelteKit (#8033)