-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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
VSCode 1.33 two main bugs on Ubuntu 18.04 #73303
Comments
Hey @fc373745, can you also please make sure you have the latest version of @types/styled-components installed? See DefinitelyTyped/DefinitelyTyped#34391 for details, both of these issue may be caused by that |
seems to be the solution. thanks! |
was fine for one day, but all of the sudden its broken with the same problems again I have reverted back to 1.31
|
Sorry i didn't read thoroughly to the referenced issue, and upon further reading, i had to DOWNGRADE |
After playing around with the versions of typescript, @types/styled-components, and vscode, i have gotten the bugs with any of the combination of these
any version of code 1.34 has a problem with matching with any of these dependencies For some reason upgrading, downgrading typescript or @types/styled-components serves as an initial solution, but after a couple of hours, it will start to break down again (weird saving behaviors, extremely slow intellisense and typescript linting/checking) The best way i can mitigate this is to downgrade code to 1.31 and it actually has the best result. here is what i'm using.
Really weird things happening, might give up styled-components and go back to css modules after this 😭 |
Duplicate of microsoft/TypeScript#30819. Please try using the latest VS Code insiders build |
Here are the bugs i've been noticing on Ubuntu 18.04 even despite disabling extensions and changing to default settings.
Steps to Reproduce:
By the lack of open issues about this has me worried that i'm an extreme edge case and that it has to do more with my machin than vscode, but please still check it out. It's been bugging me since 1.32
Does this issue occur when all extensions are disabled?: Yes/No
Yes
I have to revert my code to version 1.31 to have these issues mitigated. I say mitigated because i'm still having the saving issue on 1.31, but the intellisense is what it should be.
The text was updated successfully, but these errors were encountered: