2 Pull requests opened by 1 person

• fix: more robust solution project check for ts < 5.7 in ts plugin

  #2758 opened May 7, 2025

• fix: deduplicate definition for rune-mode components

  #2759 opened May 14, 2025

8 Issues closed by 1 person

• Svelte 5: [svelte-code] hover and watch not working with runes

  #2703 closed May 14, 2025

• @starting-style is reported as an unknown at rule by svelte-check

  #2595 closed May 7, 2025

• TypeScript + Snippet: Error about using uninitialized variable

  #2653 closed May 7, 2025

• Using @position-try produces a warning

  #2665 closed May 7, 2025

• Error referencing properties of destructured variables

  #2671 closed May 7, 2025

• export const function is declared but its value is never read

  #2717 closed May 7, 2025

• Generic type doesn't work with `extends`

  #2727 closed May 7, 2025

• Component suggestions working only at certain lines

  #2742 closed May 7, 2025

4 Unresolved conversations

Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.

• When using SvelteKit in a VSCode workspace, scss import statements like `@use` inside of style tags in components show IDE errors using virtually any path, but compile in the dev server

  #2751 commented on May 9, 2025 • 0 new comments

• Bug: Duplicate "Go to Definition" Results for Components in Svelte 5 in Neovim

  #2697 commented on May 14, 2025 • 0 new comments

• Any way to increase memory for VS code extension?

  #2725 commented on May 14, 2025 • 0 new comments

• Support custom events on native DOM elements

  #431 commented on May 14, 2025 • 0 new comments