svelte-preprocess-delegate-events
svelte-preprocess-delegate-events copied to clipboard
chore(deps): update dependency svelte-check to v4
This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| svelte-check | 3.8.6 -> 4.3.3 |
Release Notes
sveltejs/language-tools (svelte-check)
v4.3.3
Patch Changes
-
fix: prevent file watcher issue (#2859)
-
fix: allow
undefinedandnullvalues for#eachin Svelte 5 (#2863) -
perf: check if file content changed in tsconfig file watch (#2859)
v4.3.2
Patch Changes
-
perf: tweak some snapshot hot paths (#2852)
-
perf: more precise module cache invalidation (#2853)
-
fix: properly handle
runes={false}in<svelte:options>(#2847)
See https://github.com/sveltejs/language-tools/releases
v4.3.1
fix: handle object literal in MustacheTag (#2805)
v4.3.0
- feat: zero types for params (#2795)
- feat: add
awaitsupport (#2799) - fix: strip doctype using AST instead of regex (#2798)
- chore: make human output more concise and readable (#2748)
v4.2.2
- fix: invalidate project file cache and handle watcher race condition (#2779)
- fix: prevent error with bind:this={get, set} (#2781)
- fix: don't treat derived imported from svelte/store as a potential store (#2780)
- fix: key block can have its own block scope (#2768)
v4.2.1
- feat: support generics on snippets (#2761)
v4.2.0
v4.1.7
- fix: robustify hoisting logic around prop types (#2740)
- fix: ensure typed exports are marked as used (#2746)
- chore: bump vscode-html/css-language-service (#2752)
- fix: ensure eligible snippets can be referenced in module script (#2753)
- fix: prevent error with unclosed tag followed by LF or end of file (#2750)
v4.1.6
- fix: prevent unused variable error for bindable
- fix: ensure exports in runes mode are marked as used
- fix: add color CLI options
v4.1.5
- fix: take other snippets into account when checking for hoistability (#2668)
- fix: disambiguate render in module script (#2667)
- fix: properly transform $props.id when $props is assigned to props (#2694)
- fix: handle booleanish popover (#2702)
- chore: bump vscode-html/css-language-service (#2677)
- fix: use referenced project's compiler option to get resolution mode (#2676)
v4.1.4
- fix: don't hoist types/snippets referencing stores or destructured variables (#2661)
v4.1.3
- fix: move snippets to correct place when only module script present
v4.1.2
- feat: support generics attribute for JSDoc (#2624)
- fix: better snippet/interface hoistability analysis (#2655)
- chore: TypeScript 5.7 support (#2585)
v4.1.1
- fix: support each without as (#2615)
v4.1.0
- fix: don't move appended content from previous node while hoisting interface (#2596)
- fix: ensure hoisted interfaces are moved after hoisted imports (#2597)
- fix: preserve bind:... mapping on elements for better source maps
- feat: prepare for some upcoming features of Svelte 5
v4.0.9
- fix: detect shadowed variables/types during type hoisting (#2590)
v4.0.8
- fix: fall back to any instead of unknown for untyped $props (#2582)
- fix: robustify and fix file writing (#2584)
- fix: hoist types related to $props rune if possible (#2571)
v4.0.7
- fix:
$props: infer types for$bindable, infer function type from arrow function
v4.0.6
- chore: autotype
const load = ...declarations (#2540) - chore: provide component instance type in Svelte 5 (#2553)
- chore: support typescript 5.6 (#2545)
- fix: infer object and array shapes from fallback types (#2562)
v4.0.5
- fix: include named exports in svelte 5 type (#2528)
v4.0.4
- fix: relax component constructor type (#2524)
v4.0.3
- breaking(svelte5): only generate function component shape in runes mode (#2517). This means you can no longer just do
Componentin type positions. Instead you need to prepend it withtypeof. Here's how you do it:- ...when typing a component instance: Before:
let x: Component. After:let x: ReturnType<typeof Component> - ...when typing a component constructor/function: Before
let x: typeof Component. Afterlet x: typeof Component(no change)
- ...when typing a component instance: Before:
- fix: revert additional two-way-binding checks as they were causing bugs (#2508)
- fix: include files indirectly belonging to a project into correct project (#2488)
- fix: check project files update more aggressively before assigning service (#2518)
- chore: upgrade to chokidar 4 (#2502)
v4.0.2
- fix: ensure components typed through Svelte 5's
Componentinterface get proper intellisense
v4.0.1
- fix: remove ancient
processaugmentation from internald.tsfile
v4.0.0
- chore: bump magic-string (#2476)
- chore: switch from fast-glob to fdir (#2433)
- fix: detect
- feat: better type checking for bindings in Svelte 5 (#2477)
- feat: replace svelte-preprocess with barebones TS preprocessor (#2452)
- feat: project reference support (#2463)
Breaking changes
- require Svelte 4 or later (#2453)
- make TypeScript a peer dependency, require TS 5 or later (#2453)
- require node 18 or later (#2453)
processaugmentation (declaring aprocess.browserfield) was removed- slight changes to how files are assigned to which tsconfig.json (#1234, #2463)
- slight changes to how Svelte module resolution works;
.sveltefiles now take precedence over.svelte.js/tsfiles (if both exist) (#2481) - language-server now forces fewer TypeScript options. Most notably
skipLibCheckis no longer forced totrue, which may result ind.tsfiles now being checked in your project, which they were not before, revealing type errors. Either fix those or add"skipLibCheck": trueto yourtsconfig.json(#1976, #2463)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
⚠️ No Changeset found
Latest commit: 91a6b4c4f7754588bf0b8fea81f1623cea2b4e53
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR