language-tools
language-tools copied to clipboard
sveltejs
The Svelte Language Server, and official extensions which use it
### Describe the bug Related issues: - [emitDts should print diagnostic messages](https://github.com/sveltejs/language-tools/issues/1835) Hey! I'd like to maybe bring back the above issue to life, since I believe to have found...
### Describe the bug Following the `@sveltejs/enhanced-img` docs, we can style images by targeting them as `img`. https://kit.svelte.dev/docs/images#sveltejs-enhanced-img-intrinsic-dimensions However, this shows an unused css warning when using the Svelte VSCode...
#2130 Porting VSCode's implementation/reference code lens. This is not enabled by default. To enable this, you'll need to enable the `typescript.implementationsCodeLens.enabled` config or the `typescript.referencesCodeLens.enabled` config for `lang="ts"` and `javascript.referencesCodeLens.enabled`...
### Describe the bug There is a known [bug / inconvenience in VSCode](https://github.com/microsoft/vscode/issues/11173): if you don't open any *ts/*js files in your project, you can not find symbols defined there...
### Describe the bug I am trying to create a streaming response in an `+server.ts` endpoint, but `svelte-check` tells me an `AsyncIteratable` is not a `BodyInit`, I don't know why....
### Describe the bug If you quick fix a lint warning in a script block, it inserts an HTML comment at the bottom instead of a JS comment in the...
### Description When entering a class name in HTML, it would be nice to see autocompletion for global selectors defined in an outside `.css` file. ### Proposed solution Example: ```html...
### Describe the bug The plugin won't initialize when the project folder contains two or more symbolic links that point to the root of the project and as a result...
### Describe the bug When using a generic in a component, vscode suggestion list only shows the default value of the generic instead of what it extends. ### Reproduction Test.svelte...
### Context When working in a monorepository, it is possible to end up with the following structure: * **package-a** * tsconfig.json * **package-b** ➡️ *depends on package-a* * tsconfig.json ➡️...
