-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Refactor Svelte preprocess integration handling #5901
Conversation
🦋 Changeset detectedLatest commit: 47be52c The changes in this PR will be included in the next version bump. 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 |
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.
This PR is blocked because it contains a minor
changeset. A reviewer will merge this at the next release if approved.
Going out with the next major
Changes
Fixes #5899
The Svelte integration beta uses
vitePreprocess
to preprocess files, this will cause users that migrate (especially those installed hoisted like npm) to lose VSCode intellisense in Svelte files.This PR add this migration guide, and changes the fallback preprocess logic to prevent
vitePreprocess
added twice, which might be wasteful (NOTE: Double preprocessing was an issue for pnpm users before)Testing
Tested manually for the
astro add svelte tailwind
command in the examples which still work.The existing test should pass as they're not affected by the breaking change.
Docs
I've updated the Svelte integration README for information of getting intellisense to work too.