-
-
Notifications
You must be signed in to change notification settings - Fork 416
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
Update to 2.0.7 #4130
Comments
After upgrading to 2.0.7, I also got errors in VSCode output console.
I also downgraded to 2.0.6 and the extension stopped crashing. |
Will the problem still occur if you enable @dcartwright07 Since the error message is different, I'm not sure if you have the same issue. If anyone can help me debug this issue via remote desktop, please contact me in the Vue discord server. |
Pinged you in paid and trying to find you in discord but unsure where to find you in |
What did you do to Diagnose this issue? |
I got same issue. |
It still occur after enabled |
When enabled service 2 crashed on file:///Users/......./***.vue?virtualCodeId=script_ts No service provide typescript/languageService
......repeatedly |
I currently have no clue as to how this problem occurs, I need to identify where the error is being thrown first. If you want to try debugging: https://github.com/vuejs/language-tools#contribution-guide
You can ignore it, it's just harmless logs. |
@johnsoncodehk When I am not sure if this helps but I did get the same error message as @CharnaceRegis. The error messages I posted earlier was after I click to view the error log. |
Fix this issue using VS Code v1.88.0. |
I agree with that. Insiders version of VS Code. Unfortunately, l don't have any code completion |
It's crazy how annoying this bug can be. |
you can still rollback to the previous release and have it working again |
I had to rollback to 1.8.27. But the problem is the package |
The JS/TS language service immediately crashed 5 times. The service will not be restarted. This may be caused by a plugin contributed by one of these extensions: Vue.volar. Please try disabling these extensions before filing an issue against VS Code. It aways cause this error since 2.x. I downgrade to v1 to fix this issue. The vscode output logs: |
I got the same issue. Do I have to downgrade the plugin or upgrade vscode to solve it? I have not received the vscode 1.88 update yet.
|
Using VS Code Insiders fixed the issue for me. |
Here similar situation. Directly after starting VSC and opening a Vue file. log preview - click to open
Setup:
|
Also happening to me. |
VS Code v1.88 scheduled for release on 4/4. |
Shouldn't this be reverted in a |
|
2.0.8 has the same problem. |
Same here on MacBook Pro 2023, M2 Pro, macOS 14.2.1
|
This is an unpredictable error that occurs in random projects and environments. It was not occur in self-test and 3 months alpha test. To be honest, it's not fair to blame the extension for Node bugs. We could not anticipate that the Node version of the stable VSCode bundled would be unstable. Closed since VSCode 1.88 has been released. |
Download the latest https://code.visualstudio.com/. |
Since 2.0.7,
[Error - 17:06:43] Client Vue: connection to server is erroring.
write EPIPE
[Error - 17:06:43] Client Vue: connection to server is erroring.
write EPIPE
Shutting down server.
[Error - 17:06:43] Client Vue: connection to server is erroring.
write EPIPE
Shutting down server.
[Error - 17:06:43] Client Vue: connection to server is erroring.
write EPIPE
Shutting down server.
[Error - 17:06:43] Client Vue: connection to server is erroring.
write EPIPE
Shutting down server.
[Error - 17:06:43] Server process exited with signal SIGBUS.
[Error - 17:06:43] Connection to server got closed. Server will not be restarted.
Apple M1 - 16Go
I've downgraded to 2.0.6
The text was updated successfully, but these errors were encountered: