-
-
Notifications
You must be signed in to change notification settings - Fork 594
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 crash, resolved by upgrading typescript #1054
Comments
I just wanted to add on to what @zbjornson said, But this fact was forgotten for a few days and was scratching my head why I was still getting old issues for typescript being reported. Now I have global and local versions of typescript installed @ 3.2.2 and everything seems to be fine so far. 🤞 |
Here are some context why it's still in 2.8: How did you upgrade to 3.2.2? Did you go to The new It's simple as:
|
@octref thanks for the context. You linked #913 twice btw. That talks about TS 3.0, so perhaps whatever that issue was is resolved now in 3.2. I don't see high CPU usage currently. Yes on the 2nd part, I ran |
Yeah, Vetur should be able to work with any version of TypeScript. Maybe I should allow another path pointing to a specific ver of TypeScript, like VS Code: {
"typescript.tsdk": "/usr/local/lib/node_modules/typescript/lib"
} And I meant to link to #922. |
@zbjornson Oh god, many thanks for the steps provided. I never got TypeScript working since I installed Vetur. Just updated TypeScript of Vetur to 3.4.5 with the steps provided in this ticket and the extension now finally works. ❤️ |
BTW now |
Info
Problem
This is sort of a lame issue report, but I was getting a consistent crash ("the vue language server crashed 5 times in the last 3 minutes") in a large project, occurring in the typescript package running within vetur's language server. When I upgraded typescript from 2.8.4 (specified in package.json) to latest (3.2.2), the crash went away. That also seems to have improved performance significantly. You might want to consider officially upgrading that package.
The text was updated successfully, but these errors were encountered: