Skip to content

Releases: sveltejs/language-tools

101.6.0

30 Jul 06:30
fbb9496
Compare
Choose a tag to compare
  • Type check event forward from element on component #303
  • Mark props as optional in ts when initialized but no typings given #370
  • Fix svelte component rename when using bind:this #308
  • Wrap template with callback to fix used before assigned error #310
  • Fix await type checking, can now be used with PromiseLike / anything #358
  • Fix swallowing used before assigned error #277
  • Fix store.set in reactive statement #380

101.5.0

28 Jul 06:22
c0a21b4
Compare
Choose a tag to compare
  • Add note about uninstalling the old Svelte extension #372 - do this if you haven't already.
  • SvelteAction typing fix: allows void as return value #365
  • Reintroduce Svelte tag completions, add snippets to completions #364, #368
  • Fix imports done through code actions #343
  • Split regex to avoid heavy computation when there are comments at the beginning of a file #337
  • Basic Pug syntax highlighting #371
  • Fix/cleanup style attribute typing #345

101.4.0

27 Jul 06:04
5348104
Compare
Choose a tag to compare
  • Support for Svelte Native (#351), also fixes namespace clashing with React types (#228)
  • Exported functions/consts/classes of a component are now visible on the components type (#307)
  • Reactive assignments no longer implicitely have type any (#360)
  • Fix 'Variable is used before being assigned' error when using bind:this in strict mode (#338)
  • Fix type checking getting "disabled" when using directives (#352)
  • Fix dblclick event type (#357)
  • Add resize event to svelte:window (#348)
  • Editor syntax highlighting: Svelte components in template now marked as support.class.component.svelte (#321)

101.3.0

18 Jul 03:59
ffafc2d
Compare
Choose a tag to compare
  • fix svelte2tsx parentheses overwrite issues #302
  • temporarily relax event type #313
  • improve for auto import completion #317
  • syntax highlight for svelte component tags #318

101.2.0

10 Jul 06:46
514187d
Compare
Choose a tag to compare
  • Markdown syntax highlighting #301
  • Prevent name clashes when importing something with the same name as the svelte file #294

101.1.1

08 Jul 10:06
0bbbf8b
Compare
Choose a tag to compare
  • Support optional chaining and nullish coalescing (introduced in svelte 3.24) #274
  • Possibility to add component documentation #280
  • Support default languages (introduced in svelte-preprocess 4.0) #291
  • Fix incorrect semicolon error before dollar label #289
  • Initialized props (export let bla = 'blubb';) are marked as optional now #276

101.0.0

06 Jul 08:50
6f30321
Compare
Choose a tag to compare
  • New "Extract into component" refactoring (simple version) #262
  • Better typing for union types in reactive assignments and props #214
  • Props with default values are now marked as optional #276
  • Docs restructuring, FAQ/Troubleshooting for TypeScript #275
  • Hover info now contains docs #281
  • More bindings for svelte:window #265
  • Grave accent wrapping #264

BREAKING CHANGE

Adjusted svelte.config.js interface #270

If you want to pass svelte compiler options to the svelte language server (which you probably never will/need to do), you now need to pass them inside compilerOptions. Note that preprocess stays where it was before, so you are most likely not affected by this change.

Before:

svelte.config.js:

module.exports = {
   dev: true,
   preprocess: ...
};

After:

svelte.config.js:

module.exports = {
   compilerOptions: {
      dev: true
   },
   preprocess: ...
};

This was done as an attempt to harmonize/standarize svelte.config.js and open up its usage to other tools.

100.1.0

01 Jul 07:28
9b936fc
Compare
Choose a tag to compare
  • Better error messages for preprocessors #240
  • script/style extraction: handle self-closing tags #251
  • Trigger diagnostics on ts/js save #237
  • onEnter rules #244
  • Bugfixes

First production release

27 Jun 14:37
Compare
Choose a tag to compare

This release marks the first official prod release of the Svelte for VSCode extension. After a few months in beta and valuable feedback and help from the community, we feel now is the time. Thanks to everyone who helped us find and fix issues!