-
Notifications
You must be signed in to change notification settings - Fork 151
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
formatOnSave & autocomplete became slower after update with Deno 1.37.0 #931
Comments
For a temporary solution, use {
"deno.enable": true,
"deno.lint": true,
"deno.codeLens.test": true,
"editor.formatOnSave": true,
"deno.importMap": "import_map.json",
"editor.defaultFormatter": "esbenp.prettier-vscode",
"[typescriptreact]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[typescript]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[javascriptreact]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[javascript]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[css]": {
"editor.defaultFormatter": "vscode.css-language-features"
}
}
|
CC @nayeemrmn can you take a look? |
It not works, btw. So i downgrade to 1.36.4 -- and the problem is gone. |
@ynwd If the problem is still there when changing the default formatter, it's not the formatter that's slow. Is it just the LSP in general being unresponsive? I can't see anything like that. Can you give a more detailed reproduction e.g. a sample file in a new project? |
@nayeemrmn |
@ynwd Looks like this is the same as denoland/deno#20136. Watch that issue for updates. |
on a very small project (like hello world http server), this problem is not found. but when I switch to the bigger one (with watch mode and a complex import_map -- fullstack apps), this problem is found again. so my temporary solution is back to use previous version (v1.36.4) |
Closing in favour of #943. Thanks for reporting |
Describe the bug
formatOnSave
and autocomplete became slower after update with Deno 1.37.0what actually happened?
Operating System
The text was updated successfully, but these errors were encountered: