chore(deps-dev): bump eslint-plugin-solid from 0.15.0 to 0.16.0 in /extension

[dependabot]

Bumps eslint-plugin-solid from 0.15.0 to 0.16.0.

Release notes

Sourced from eslint-plugin-solid's releases.

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 exempt.
• New rule solid/prefer-structured-class (warning in v2, error in v2-strict): nudges manually-built class strings (concatenation with conditionals, conditional template literals, .join(" ")) toward the structured array/object ClassValue forms that Solid 2.0 accepts natively. Static strings and plain interpolation are untouched.
• New rule solid/no-module-scope-reactive-primitive (error in v2-strict only): reactive state at module scope is shared across SSR requests. createRoot-wrapped module state is the deliberate escape hatch and is not flagged.
• New rule solid/prefer-onSettled-for-side-effects (warning in v2-strict only): flags side-effectful setup (timers, global listeners, observers) in component bodies, where it also runs during SSR; suggests onSettled. Never flags onCleanup itself.
• New rule solid/no-restated-default-options (error in v2-strict only, autofixable): removes restated defaults like <For keyed={true}> and <Show keyed={false}>.
• Version-2 behavior in existing rules (active when settings.solid.version is 2):
  • solid/no-unknown-namespaces inverts its premise: namespaces are no longer reserved in 2.0, so any colon-name is a legal literal attribute — but the formerly-special prefixes use:, attr:, bool:, on:, and oncapture: are flagged as near-certain 1.x migration bugs with per-prefix guidance. prop: remains the only special namespace.

... (truncated)

Commits

• 65eaef5 Merge pull request #212 from solidjs-community/v0.16.0
• 7feef41 v0.16.0
• 010b2f1 feat: Solid 2.0 rule layout — v2/v2-strict configs, seven new rules, version-...
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)