Repository navigation
Update dependency eslint-plugin-svelte to v3.24.1 - #78
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/eslint-plugin-svelte-3.x-lockfile
branch
from
October 20, 2026 18:33
c4823f5 to
f55c8fd
Compare
renovate
Bot
force-pushed
the
renovate/eslint-plugin-svelte-3.x-lockfile
branch
from
November 3, 2026 23:47
f55c8fd to
a68e252
Compare
renovate
Bot
force-pushed
the
renovate/eslint-plugin-svelte-3.x-lockfile
branch
from
November 7, 2026 13:50
a68e252 to
df47ade
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.23.0→3.24.1Release Notes
sveltejs/eslint-plugin-svelte (eslint-plugin-svelte)
v3.24.1Compare Source
Patch Changes
#1665
4b06717Thanks @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
fbae40aThanks @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 unlesscheckAsyncFunctionsis enabled, and functions that return a Promise of a value (e.g.Promise<string>) are now ignored even whencheckAsyncFunctionsis 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
d5ad32aThanks @officialasishkumar! - fix: recognize<script module>inno-export-load-in-svelte-module-in-kit-pagesandprefer-destructured-store-propsv3.24.0Compare Source
Minor Changes
8cca2e0Thanks @marekdedic! - feat(no-navigation-without-resolve): track resolve() through array elements, object properties and {#each} iteration variablesPatch Changes
#1380
9944910Thanks @baseballyama! - fix(no-navigation-without-resolve): check completereltokens before exempting external links#1566
e49015dThanks @arpitjain099! - fix(no-unused-props): fix false positives and negatives around spreads, aliases, dotted keys, and props that share a type#1516
7538afaThanks @kevin-easygo! - fix(no-reactive-functions): useisSpaceBetweeninstead ofisSpaceBetweenTokens, which was removed in ESLint v10#1618
7999ad4Thanks @baseballyama! - fix(valid-compile): read the parser fromcontext.languageOptions.parserOptions, sincecontext.parserOptionswas removed in ESLint v10#1606
78def78Thanks @ozenyunus35! - Allow a comment before a closing token insvelte/indentto be aligned with the previous line instead of requiring the indentation of the closing token.#1581
3b308f3Thanks @badreddinesaadioui! - fix(prefer-svelte-reactivity): stop reporting in legacy (non-runes) components, where thesvelte/reactivityclasses are not tracked#1627
36abd30Thanks @baseballyama! - Fix false positives insvelte/no-unused-props: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 asuser.name.$inspect(props)orfn(props)). Every property now counts as used. A type query liketypeof props.ais not counted as a use.user[key]now counts as using every property ofuser.props[0].aandprops[`a`], and wrapped values likeprops!.a,(props as Props).aand(props satisfies Props).aare now tracked.allowUnusedNestedProperties, nested properties are never reported.#foo,private,protected) are no longer reported, e.g. in intersections.#1629
5e0c7bfThanks @baseballyama! - Stopsvelte/no-unused-svelte-ignorefrom reportingsvelte-ignorecomments for runtime warnings (e.g.ownership_invalid_binding), which the compiler can't report.#1626
9aa3a7aThanks @baseballyama! - Requirepostcss@^8.5.10to avoid GHSA-qx2v-qp2m-jg93.#1613
80e66ecThanks @smile-alive! - fix(sort-attributes): do not report or move shorthand attributes and directives across spread attributes#1635
cf11995Thanks @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 asgetContext()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
a972353Thanks @eknathdj! - Honorsvelte-ignorecomments on nested script nodes insvelte/no-unused-svelte-ignoreandsvelte/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
ae85b36Thanks @baseballyama! - chore: updatesvelte-eslint-parserto 1.10.1#1625
9b859e3Thanks @baseballyama! - PasscompilerOptions.runesfrom the Svelte config to the compiler insvelte/valid-compileandsvelte/no-unused-svelte-ignore, so runes-mode warnings are reported for files that rely onrunes: true. The function form (runes: ({ filename }) => ...) is also supported.v3.23.1Compare Source
Patch Changes
#1592
ed67eb7Thanks @baseballyama! - Exclude deprecated rules from theallconfiguration while keeping active rules enabled.#1594
af288cdThanks @baseballyama! - Recognizebrowserfrom SvelteKit's$app/envalias as a browser guard inno-top-level-browser-globals.#1588
9814b51Thanks @baseballyama! - Include all active extension rules in the Extension Rules documentation table while preserving their primary-category entries.#1589
57863c5Thanks @baseballyama! - Keep the documented project service configuration consistent across TypeScript and Svelte files to avoid unnecessary project reloads.#1593
4ad2c67Thanks @baseballyama! - Limitrequire-each-keydiagnostics to the opening each tag instead of the whole block.#1599
90d7b09Thanks @baseballyama! - Enable no-navigation-without-resolve on SvelteKit 3 so the recommended config reports internal links and navigation calls that omit resolve().#1590
a28563fThanks @baseballyama! - Fix false positives inno-immutable-reactive-statementsfor TypeScript components whenecmaFeatures.globalReturnis enabled.#1598
4607a2cThanks @baseballyama! - Recognize SvelteKit 3 in rule conditions, including prereleases, and document version detection and routes configuration.Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.