-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
Load language integrations from the user project #332
Conversation
🦋 Changeset detectedLatest commit: 7a25698 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
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 |
…nal-language-integrations
@@ -1,5 +1,6 @@ | |||
.github |
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 is unrelated to this specific PR, just something I missed in #334
|
||
if (diagnostic.message.includes('.vue')) { | ||
diagnostic.message += | ||
'\n\nIs the `@astrojs/vue` package installed? You can add it to your project by running the following command: `astro add vue`. If already installed, restarting the language server might be necessary in order for the change to take effect'; |
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.
like these suggestions!
Just needs a changeset. |
This reverts commit 4b73c21.
…"" This reverts commit c8c29ee.
Changes
Editor tooling part of withastro/astro#3864
This deprecate both
@astrojs/svelte-language-integration
and@astrojs/vue-language-integration
This makes the language-server about 600 files lighter and about 10mb~ less. Since we need those integrations in dev, this only affects users and not developers, but that's okay
Testing
Our current tests already cover importing and doing stuff with Vue and Svelte components. Adding the integrations as dev dependencies is enough to have them inside fixtures
Not sure if anything more is needed here, testing the package imports would be testing that Node's require work
Docs
Will tell people in my announce message. I'll monitor #support-threads after to see if we need to document this more heavily or not, it shouldn't technically affect many people (if you're using Svelte, you're likely to have the Svelte integration, I think?)