-
-
Notifications
You must be signed in to change notification settings - Fork 414
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
Server crashes every time I try to make a <style> #4520
Labels
bug
Something isn't working
Comments
It also happened to me when create a new vue file. |
facing same issue. |
same issue |
This was referenced Jul 3, 2024
Related to
|
我以为电脑问题呢 还真是插件啊 |
Same too when add new teamplate tag |
This was referenced Aug 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Vue - Official extension or vue-tsc version
v2.0.24
VSCode version
1.90.2
Vue version
^3.4.18
TypeScript version
^4.5.4
System Info
Steps to reproduce
Create a component and start typing a <style lang="scss" scoped> tag.
What is expected?
The vscode extension doesn't crash.
What is actually happening?
The vscode extension crashes with the above error:
TypeError: Cannot read properties of undefined (reading 'label')
at Dte (/home/user/.vscode/extensions/vue.volar-2.0.24/dist/server.js:13571:2319)
at Object.provideCompletionItems (/home/user/.vscode/extensions/vue.volar-2.0.24/dist/server.js:13571:1995)
at async m (/home/user/.vscode/extensions/vue.volar-2.0.24/dist/server.js:2:48796)
at async Object.getCompletionItems (/home/user/.vscode/extensions/vue.volar-2.0.24/dist/server.js:2:49560)
at async /home/user/.vscode/extensions/vue.volar-2.0.24/dist/server.js:66:20287
at async Timeout. (/home/user/.vscode/extensions/vue.volar-2.0.24/dist/server.js:66:26830)
Node.js v20.9.0
[Error - 2:27:59 PM] Server process exited with code 1.
[Error - 2:27:59 PM] The Vue server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
Link to minimal reproduction
No response
Any additional comments?
If I revert to v2.0.22 everything works as expected.
The text was updated successfully, but these errors were encountered: