You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cool. If you have more suggestions go ahead.
I am planning to update and publish new version. Since tooling has improved a lot since last version. Originally posted by @mubaidr in #14 (comment)
As requested for suggestions, I decided to open an issue to discuss options and allow others to contribute.
This one is more recently updated and may be more actively maintained.
I'm unsure if the pack should prefer one over the other, but I wanted to highlight a possible alternative.
I noticed that the extension which is already in the pack:
Although that looks like a deprecation warning, it means to disable the native TS language server in VS Code while using the extension, which allows the Volar language server to "take over" handling regular TS files and Vue SFC files with TS.
The instruction is more clearly stated on the Official Vue Page
The configuration change is significant. Otherwise, two language servers are parsing TS, which impacts performance.
Maybe the extension pack should call attention to the instructions since the extension cannot automate the change.
Since the update will be forward-looking, maybe the extension pack should include Official Vite and Vitest extensions:
As requested for suggestions, I decided to open an issue to discuss options and allow others to contribute.
The pack already includes:
But this extension hasn't been updated in 2 years, and the repo still says "Vue 2" even though the Marketplace lists "Vue 3".
There's a similar extension with ~1.5m installs:
This one is more recently updated and may be more actively maintained.
I'm unsure if the pack should prefer one over the other, but I wanted to highlight a possible alternative.
I noticed that the extension which is already in the pack:
says:
Although that looks like a deprecation warning, it means to disable the native TS language server in VS Code while using the extension, which allows the Volar language server to "take over" handling regular TS files and Vue SFC files with TS.
The instruction is more clearly stated on the Official Vue Page
The configuration change is significant. Otherwise, two language servers are parsing TS, which impacts performance.
Maybe the extension pack should call attention to the instructions since the extension cannot automate the change.
Since the update will be forward-looking, maybe the extension pack should include Official Vite and Vitest extensions:
The text was updated successfully, but these errors were encountered: