Bump eslint-plugin-solid from 0.14.5 to 0.16.1 in /registration/frontend in the minor-and-patch group

[dependabot]

Bumps the minor-and-patch group in /registration/frontend with 1 update: eslint-plugin-solid.

Updates eslint-plugin-solid from 0.14.5 to 0.16.1

Release notes

Sourced from eslint-plugin-solid's releases.

v0.16.1

A precision pass over solid/reactivity, driven by the longest-standing false-positive reports in the tracker. Every fix landed with a regression test reproducing the original issue, and the Solid 2.0 templates still lint clean.

Fixes

• Context provider value gets a real explanation (#209). Passing a reactive expression to a provider's value prop previously produced the generic "should be used within JSX" message — nonsense for something that is in JSX. It now reports a dedicated message explaining that providers read value once, untracked, when created (true in both Solid 1.x and 2.0), and to pass the signal, memo, or store itself. Detection also now covers the Solid 2.0 form, where the context object is used directly as the provider (<MyContext value={...}>), by resolving JSX names to createContext() calls.
• createResource argument shapes (#199, #195). createResource(fetcher, options) no longer treats the fetcher as a tracked scope (so async fetchers with an options object stop reporting noAsyncTrackedScope), and in createResource(source, fetcher) the fetcher is now correctly treated as an untracked called function that may be async and read current values. The source remains a synchronous tracked scope.
• Destructuring props inside a tracked scope (#191). const { item } = props inside createMemo/createEffect re-runs on updates and no longer warns. Destructuring at component setup level still does.
• window.setTimeout and friends (#194). Timer and scheduling callbacks prefixed with window., globalThis., or self. now get the same called-function treatment as the bare globals.
• mergeProps/merge function arguments are tracked scopes (#179). Both wrap function sources in createMemo, so reactive reads inside them no longer warn.
• Memos passed to functions are as safe as signals (#182). Passing a createMemo accessor to a create*/use*/custom reactive function no longer warns, matching the existing allowance for signals.
• Directly-returned create* calls (#52). return createMemo(...) (or as an arrow body) no longer reports shouldAssign — the result is handed to the caller, like a custom primitive.
• Functions passed to calls inside tracked scopes (#197). An inline function passed to an unknown call inside an effect (doSomething(() => props.toggle)) no longer warns, matching the existing behavior for named functions: synchronous calls still run tracked, and later calls poll current values.

Features

• Patterns in customReactiveFunctions (#176). Entries now support * wildcards ("watch*") and regexes written as "/pattern/" strings, in addition to exact names.

v0.16.0

The complete Solid 2.0 lint surface: version-aware rules, new v2 / v2-strict configs, and a full set of 2.0-specific rules, all vetted against the official Solid 2.0 templates (which lint clean with zero errors and zero warnings under the v2 config).

Features

• settings.solid.version. Rules can now read the targeted Solid major version from ESLint settings (settings: { solid: { version: 2 } }). Unset means the permissive dual-version behavior from 0.15. The new configs preset it; any custom config can opt in with one line.
• New v2 config (eslint-plugin-solid/configs/v2, also solid.configs.v2): what the official Solid 2.0 templates ship. Sets the version setting, switches existing rules to strict 2.0 semantics, and enables the new 2.0 rules — errors are reserved for near-certain bugs, heuristics stay warnings.
• New v2-strict config (eslint-plugin-solid/configs/v2-strict): everything in v2 plus the plugin's strongest opinions (see below).
• New rule solid/removed-api (error in v2): flags removed/renamed 1.x APIs with autofixes where mechanical (onMount→onSettled, batch→flush, mergeProps→merge, unwrap→snapshot, equalFn→isEqual, getListener→getObserver, classList={{...}}→class={{...}}, "solid-js/web"→"@solidjs/web", "solid-js/store"→"solid-js") and prescriptive migration messages otherwise (createResource, on, Suspense→Loading, Index→<For keyed={false}>, produce, etc.). Lists verified against the Solid 2.0 RC source.
• New rule solid/no-single-arg-create-effect (error in v2): Solid 2.0 requires the split createEffect(compute, effect) form. The single-argument 1.x form produces no TS compile error on a bare statement call and only throws at runtime in dev mode; this rule is the build-time hard stop for the most commonly reproduced AI mistake.
• New rule solid/no-accessor-as-prop (error in v2): <div title={count} /> silently renders a stringified function. Fires on any expression that statically resolves to a function in a value-typed DOM attribute, with a message that states the fix (count → count()). Event handlers, ref, children, namespaced attributes, components, and custom elements are

... (truncated)

Commits

• 3c01fbd Merge pull request #217 from solidjs-community/reactivity-precision-0.16.1
• a892c77 v0.16.1
• 0aa7bc8 fix(reactivity): precision pass over long-standing false positives
• cbd3c8a Merge pull request #216 from solidjs-community/reactivity-object-destructuring
• b123632 test: drop type assertion missing its import from object-destructuring cases
• f1ba27b merge main
• c608685 Merge pull request #215 from solidjs-community/rule-confidence-audit
• df8f435 fix: narrow FunctionNode to CallExpressionArgument in no-destructure componen...
• 105acf0 Merge pull request #214 from solidjs-community/fix-setup-read-captured-closure
• 0025b50 no-restated-default-options: treat unbound control-flow names as Solid's
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for eslint-plugin-solid since your current version.

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like eslint-plugin-solid is updatable in another way, so this is no longer needed.