Remco Haszing
Remco Haszing
I use the same version of VSCode. That’s not the problem. Do you also have this problem when you disable all other extensions?
Could you provide: - A list of your extensions. (Output of `code --list-extensions`) - A list of extensions that register TypeScript plugins. (Output of `grep -l '"typescriptServerPlugins"' ~/.vscode/extensions/*/package.json`) - Your...
That info is helpful. :) All 3 extensions you listed that provide TypeScript plugins (`styled-components.vscode-styled-components`, `svelte.svelte-vscode`, `visualstudioexptteam.vscodeintellicode`) are known to have caused conflicts with Volar. Can you try disabling them...
I’m not seeing that: - It’s resolved in `svelte.svelte-vscode`. - This still occurs when using `styled-components.vscode-styled-components`. - When using `visualstudioexptteam.vscodeintellicode` additionally, this solves it again. I imagine this has something...
I just released 1.8.5. This fixes a deeper issue which may resolve various unexpected bugs. But if you’re saying it works with 1.8.4, that should be ok, right? > Also,...
Ah, so you meant JSX elements, not HTML. They are not the same. Anyway, what you’re seeing is #267.
TypeScript error when axios instance is created from an import that uses `axios >=1.6.0`'s ESM types
I think https://github.com/axios/axios/pull/6218 would resolve the issue.
GitHub looks at the textual meaning of the blockquote content. It works fine with escaped `[` characters. --- ```markdown > \[!NOTE] > Useful information that users should know, even when...
No, sorry. I tried removing tests from that repo, but eventually the issue seemingly goes away. It also doesn’t help that the issue occurs randomly. Some additional notes: - Removing...
By a pure coincidence I found out that adding `threads: false` resolves the problem.