Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency svelte-check to v4 #157

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 2, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
svelte-check 3.8.6 -> 4.0.9 age adoption passing confidence

Release Notes

sveltejs/language-tools (svelte-check)

v4.0.9

Compare Source

  • fix: detect shadowed variables/types during type hoisting (#​2590)

v4.0.8

Compare Source

  • 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

Compare Source

  • fix: $props: infer types for $bindable, infer function type from arrow function

v4.0.6

Compare Source

  • 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

Compare Source

  • fix: include named exports in svelte 5 type (#​2528)

v4.0.4

Compare Source

  • fix: relax component constructor type (#​2524)

v4.0.3

Compare Source

  • breaking(svelte5): only generate function component shape in runes mode (#​2517). This means you can no longer just do Component in type positions. Instead you need to prepend it with typeof. 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. After let x: typeof Component (no change)
  • 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

Compare Source

  • fix: ensure components typed through Svelte 5's Component interface get proper intellisense

v4.0.1

Compare Source

  • fix: remove ancient process augmentation from internal d.ts file

v4.0.0

Compare Source

  • chore: bump magic-string (#​2476)
  • chore: switch from fast-glob to fdir (#​2433)
  • fix: detect <script module> tag (#​2482)
  • 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)
  • process augmentation (declaring a process.browser field) was removed
  • slight changes to how files are assigned to which tsconfig.json (#​1234, #​2463)
  • slight changes to how Svelte module resolution works; .svelte files now take precedence over .svelte.js/ts files (if both exist) (#​2481)
  • language-server now forces fewer TypeScript options. Most notably skipLibCheck is no longer forced to true, which may result in d.ts files now being checked in your project, which they were not before, revealing type errors. Either fix those or add "skipLibCheck": true to your tsconfig.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.

Copy link

changeset-bot bot commented Oct 2, 2024

⚠️ No Changeset found

Latest commit: 378f1c5

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

@renovate renovate bot force-pushed the renovate/svelte-check-4.x branch 2 times, most recently from 4c76805 to 30a8306 Compare October 6, 2024 22:39
@renovate renovate bot force-pushed the renovate/svelte-check-4.x branch 2 times, most recently from 0fd2abf to 8e586f6 Compare October 14, 2024 21:17
@renovate renovate bot force-pushed the renovate/svelte-check-4.x branch 3 times, most recently from c289612 to 00e36bf Compare October 27, 2024 22:30
@renovate renovate bot force-pushed the renovate/svelte-check-4.x branch from 00e36bf to ef6e74d Compare November 10, 2024 15:13
@renovate renovate bot force-pushed the renovate/svelte-check-4.x branch 2 times, most recently from 8afaadc to 0e09279 Compare November 23, 2024 12:37
@renovate renovate bot force-pushed the renovate/svelte-check-4.x branch from 0e09279 to 0766bdc Compare November 29, 2024 09:46
@renovate renovate bot force-pushed the renovate/svelte-check-4.x branch 3 times, most recently from d843abb to d2bb1df Compare December 13, 2024 12:03
@renovate renovate bot force-pushed the renovate/svelte-check-4.x branch 2 times, most recently from bce0317 to 787d90a Compare December 16, 2024 22:48
@renovate renovate bot force-pushed the renovate/svelte-check-4.x branch from 787d90a to 378f1c5 Compare December 19, 2024 11:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants