v1.2.0

Add a new svelte-enhance crate which diverges and tries to improve upon upstream until tsgo's 7.1 stable API lands.

svelte-check-native now reports TS2307 for an import whose target doesn't exist - something svelte-check --tsgo can't do (svelte's own declare module '*.svelte' wildcard makes tsgo resolve every .svelte specifier, missing ones included, to any).

We match the default svelte-check instead, across every import form, and fix a comma-reactive false positive along the way.

Added

• Missing .svelte imports → TS2307, matching the default svelte-check. Covers relative (./x.svelte), aliased ($lib/x.svelte via tsconfig paths), bare (pkg/x.svelte via node_modules + package.json exports), and dynamic import('./x.svelte') — resolved with oxc_resolver, so a diagnostic fires only on a genuine on-disk miss. A workspace declaring its own declare module '*.svelte' disables the check (no false positive). Isolated in a droppable svn-enhance crate. 62ea5071..67225867
• --disable-enhance flag (and SVN_DISABLE_ENHANCE env var) to turn the tsgo-mode enhancement checks off at runtime. 67225867

Fixed

• No false TS2695 on Svelte-4 comma-separated reactive statements ($: a, b, c, expr) — the default engine filters these for reactive deps; --tsgo leaked them (sveltejs/language-tools#2973). 12b2b2d9

Internal

• Locked +page.svelte route-data typing against upstream #3061 (we already type data as PageData, not any). 2c4f3161