Skip to content

Update dependency eslint-plugin-svelte to v3.24.1 - #78

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/eslint-plugin-svelte-3.x-lockfile
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/eslint-plugin-svelte-3.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
eslint-plugin-svelte (source) 3.23.0 → 3.24.1 age confidence

Release Notes

sveltejs/eslint-plugin-svelte (eslint-plugin-svelte)

v3.24.1

Compare Source

Patch Changes
  • #​1665 4b06717 Thanks @​officialasishkumar! - fix(prefer-derived-over-derived-by): keep type annotations, comments and sequence expressions in the autofix, and skip it when it would change the code

  • #​1414 fbae40a Thanks @​ai! - fix(require-event-prefix): ignore function props that return a value (e.g. getHref: (item: T) => string). This also changes two cases: () => Promise<void> is now ignored unless checkAsyncFunctions is enabled, and functions that return a Promise of a value (e.g. Promise<string>) are now ignored even when checkAsyncFunctions is enabled.

    Only known no-value returns are checked; any, unknown, never, and unresolved generic returns are ignored. In generic components, only explicit no-value annotations and their Promise wrappers are checked to avoid false positives from parser substitutions.

  • #​1666 d5ad32a Thanks @​officialasishkumar! - fix: recognize <script module> in no-export-load-in-svelte-module-in-kit-pages and prefer-destructured-store-props

v3.24.0

Compare Source

Minor Changes
  • #​1553 8cca2e0 Thanks @​marekdedic! - feat(no-navigation-without-resolve): track resolve() through array elements, object properties and {#each} iteration variables
Patch Changes
  • #​1380 9944910 Thanks @​baseballyama! - fix(no-navigation-without-resolve): check complete rel tokens before exempting external links

  • #​1566 e49015d Thanks @​arpitjain099! - fix(no-unused-props): fix false positives and negatives around spreads, aliases, dotted keys, and props that share a type

  • #​1516 7538afa Thanks @​kevin-easygo! - fix(no-reactive-functions): use isSpaceBetween instead of isSpaceBetweenTokens, which was removed in ESLint v10

  • #​1618 7999ad4 Thanks @​baseballyama! - fix(valid-compile): read the parser from context.languageOptions.parserOptions, since context.parserOptions was removed in ESLint v10

  • #​1606 78def78 Thanks @​ozenyunus35! - Allow a comment before a closing token in svelte/indent to be aligned with the previous line instead of requiring the indentation of the closing token.

  • #​1581 3b308f3 Thanks @​badreddinesaadioui! - fix(prefer-svelte-reactivity): stop reporting in legacy (non-runes) components, where the svelte/reactivity classes are not tracked

  • #​1627 36abd30 Thanks @​baseballyama! - Fix false positives in svelte/no-unused-props:

    • The props object is destructured (e.g. const { a } = props). A destructured key now counts as used when its binding is used, and an unused one is reported. Nested destructuring (e.g. const { name } = user) can now report unused nested properties, the same as user.name.
    • The props object is used as a whole (e.g. $inspect(props) or fn(props)). Every property now counts as used. A type query like typeof props.a is not counted as a use.
    • A dynamic key like user[key] now counts as using every property of user.
    • Numeric and template literal keys like props[0].a and props[`a`], and wrapped values like props!.a, (props as Props).a and (props satisfies Props).a are now tracked.
    • Instances of generic classes are now skipped like other class instances.
    • With allowUnusedNestedProperties, nested properties are never reported.
    • Class members that cannot be read from outside (#foo, private, protected) are no longer reported, e.g. in intersections.
  • #​1629 5e0c7bf Thanks @​baseballyama! - Stop svelte/no-unused-svelte-ignore from reporting svelte-ignore comments for runtime warnings (e.g. ownership_invalid_binding), which the compiler can't report.

  • #​1626 9aa3a7a Thanks @​baseballyama! - Require postcss@^8.5.10 to avoid GHSA-qx2v-qp2m-jg93.

  • #​1613 80e66ec Thanks @​smile-alive! - fix(sort-attributes): do not report or move shorthand attributes and directives across spread attributes

  • #​1635 cf11995 Thanks @​baseballyama! - fix(require-store-reactive-access): with type information, don't report callable stores used as functions, actions, transitions, or event handlers, and stores from function calls such as getContext() checked with ?? / ??= with a store fallback. Don't auto-fix stores that are not declared at the top level, are used in the module script, or are on the left side of ||= / &&= / ??=.

  • #​1616 a972353 Thanks @​eknathdj! - Honor svelte-ignore comments on nested script nodes in svelte/no-unused-svelte-ignore and svelte/valid-compile (Svelte 5), and no longer treat a comment at the end of the previous line as an ignore comment for the next node.

  • #​1648 ae85b36 Thanks @​baseballyama! - chore: update svelte-eslint-parser to 1.10.1

  • #​1625 9b859e3 Thanks @​baseballyama! - Pass compilerOptions.runes from the Svelte config to the compiler in svelte/valid-compile and svelte/no-unused-svelte-ignore, so runes-mode warnings are reported for files that rely on runes: true. The function form (runes: ({ filename }) => ...) is also supported.

v3.23.1

Compare Source

Patch Changes
  • #​1592 ed67eb7 Thanks @​baseballyama! - Exclude deprecated rules from the all configuration while keeping active rules enabled.

  • #​1594 af288cd Thanks @​baseballyama! - Recognize browser from SvelteKit's $app/env alias as a browser guard in no-top-level-browser-globals.

  • #​1588 9814b51 Thanks @​baseballyama! - Include all active extension rules in the Extension Rules documentation table while preserving their primary-category entries.

  • #​1589 57863c5 Thanks @​baseballyama! - Keep the documented project service configuration consistent across TypeScript and Svelte files to avoid unnecessary project reloads.

  • #​1593 4ad2c67 Thanks @​baseballyama! - Limit require-each-key diagnostics to the opening each tag instead of the whole block.

  • #​1599 90d7b09 Thanks @​baseballyama! - Enable no-navigation-without-resolve on SvelteKit 3 so the recommended config reports internal links and navigation calls that omit resolve().

  • #​1590 a28563f Thanks @​baseballyama! - Fix false positives in no-immutable-reactive-statements for TypeScript components when ecmaFeatures.globalReturn is enabled.

  • #​1598 4607a2c Thanks @​baseballyama! - Recognize SvelteKit 3 in rule conditions, including prereleases, and document version detection and routes configuration.


Configuration

📅 Schedule: (UTC)

  • 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.

@renovate
renovate Bot requested a review from PyRo1121 as a code owner October 16, 2026 21:38
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-svelte-3.x-lockfile branch from c4823f5 to f55c8fd Compare October 20, 2026 18:33
@renovate renovate Bot changed the title Update dependency eslint-plugin-svelte to v3.23.1 Update dependency eslint-plugin-svelte to v3.24.0 Nov 3, 2026
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-svelte-3.x-lockfile branch from f55c8fd to a68e252 Compare November 3, 2026 23:47
@renovate
renovate Bot force-pushed the renovate/eslint-plugin-svelte-3.x-lockfile branch from a68e252 to df47ade Compare November 7, 2026 13:50
@renovate renovate Bot changed the title Update dependency eslint-plugin-svelte to v3.24.0 Update dependency eslint-plugin-svelte to v3.24.1 Nov 7, 2026
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