Solid 1.9
Last reviewed Oct 11, 2026
Prompt Details
Prompt Composition
2prompts
- JavaScript ES2026102 lines · 3.1K tokens
- Solid 1.964 lines · 3K tokens
Total166 lines · 6.1K tokens
CWE Coverage
- 20
- 79
- 89
- 95
- 117
- 201
- 208
- 209
- 323
- 338
- 346
- 347
- 352
- 362
- 459
- 471
- 488
- 494
- 502
- 524
- 602
- 770
- 772
- 807
- 829
- 838
- 862
- 915
- 916
- 918
- 922
- 943
- 1004
- 1321
- 1333
Prompt Preview
Apply the JavaScript ES2026 prompt first. These rules cover solid-js 1.9, including solid-js/store and solid-js/web, checked against 1.9.15; review SolidStart, routers, server adapters, and build tools against their own versions.
Runtime and compiler
- Target supported hosts: the last two years of Firefox, Safari, Chrome, and Edge, supported Node.js LTS, or current Deno and Cloudflare Workers. Check build tool and adapter runtime requirements separately;
solid-js1.9.15 declares no numeric Node.js engine minimum. - Keep
babel-preset-solidand its resolvedbabel-plugin-jsx-dom-expressionson the release matchingsolid-js, moved together; rebuild all SSR artifacts after compiler or runtime updates, since compiler escaping fixes reach only recompiled output. solid-jspinsseroval/seroval-pluginswith tilde ranges (one minor's patches), while seroval fixes only its latest release. When a fix for either lands outside your range, override both to one release at or past every advisory's patched release (npmoverrides, pnpmoverridesinpnpm-workspace.yaml, or Yarnresolutions). Keep both on the same release: newer plugins import helpers older seroval lacks, so split overrides fail when the server bundle loads, and overriding only the flagged package leaves the other's advisories open. Rebuild inlining server bundles, rerun SSR tests, and drop the override once the installedsolid-jsrange admits the fix.- On
solid-js1.9.7 through 1.9.15, which predate the 1.9.16 change to serializer ranges that admit the fixes, that override is needed: