Update dependency svelte-check-native to v1.8.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
svelte-check-native	1.5.2 → 1.8.0

---

Release Notes

harshmandan/svelte-check-native (svelte-check-native)

v1.8.0

Compare Source

Adds Android (Termux) support and updates oxc.

Added

• Android arm64 (#​67). The linux-arm64 binary is now a static
  musl build, so it has no glibc dependency and the same package
  installs and runs on Android. TypeScript 7 publishes no Android
  build, so install its linux-arm64 compiler explicitly — see the
  README's Android section. The static build is within noise of the
  previous glibc one on a 1358-file workspace.

Changed

• oxc 0.148 → 0.149.

v1.7.0

Compare Source

A parity release built from a source-level audit of every place our
pipeline decides something differently from upstream svelte-check --tsgo — the svelte2tsx conversion, the diagnostic mapping and
filtering, the SvelteKit injection, the CLI surface and the compiler's
own checks — with each difference probed against upstream and ported.
The parity gate on the control workspaces was also hollow: upstream
type-checked nothing there because two components compiled to
unparsable TypeScript. It now applies a committed recipe and fails
whenever upstream could not have checked anything; both control
workspaces report exactly what upstream reports.

Fixed

• Bogus "Property 'fn' is missing" on every consumer of a
  component that exports a function (#​65). Named exports are now the
  component's instance members, as upstream types them.
• No bogus children error on a Svelte 4 install (#​63). Slot
  content becomes an implicit children prop only when Svelte 5 or
  later is installed, as svelte-check does.
• The Svelte compiler's errors are reported. svelte-check reports a
  component's first compiler error (and drops its warnings); we now
  produce the compiler's rune, state, props, store, export, declaration,
  element, directive, block, slot, snippet and svelte:options errors,
  script syntax errors (js_parse_error, with acorn's messages and
  positions, including through TypeScript's transpile when there is no
  Svelte config), typescript_invalid_feature, compile-option
  validation from the Svelte config, and the compiler's crash on a
  dotted namespace. 134 of upstream's 188 compiler-error samples match
  (was 64); the rest are CSS errors or cannot occur under svelte-check.
• Components the compiler or svelte2tsx rejects are left out of the
  run, as upstream leaves them out: templates parse() throws on, and
  inputs svelte2tsx crashes on.
• Conversion follows svelte2tsx in many more places: $: targets,
  type hoisting, slot lets, bind:this, await/key/each blocks, quoted
  directive values, attributes on elements and components, comma
  values, root snippets, default-export shape, component events,
  SvelteKit route typing and script copies, svelte:boundary, script
  tags written as <Script> or closed with </script >.
• Diagnostics land where upstream puts them, start and end: source
  maps resolve to the user text before a generated position, component
  prop keys and implicit children map like upstream, and TS1117 /
  TS7028 / TS2454 / pug drops are decided on the source.
• A syntax error in your own script is reported as yours, never as
  our internal "overlay-syntax-error".
• Output matches svelte-check: file order, human output and colours,
  NO_COLOR / FORCE_COLOR / CI, and the CLI's error messages.
• The overlay tsconfig is written as svelte-check writes it
  (rootDirs, paths order, references, types, composite, a
  tsconfig without include), and invalid include / exclude
  patterns and tsconfig syntax are rejected as TypeScript rejects them.
• Many compiler warnings now match: scopes, runes detection,
  svelte-ignore handling, bidi-character warnings (including their
  order across files), accessibility and store/rune conflicts.

Changed

• Incremental mode is opt-in (--incremental), as in svelte-check.
  A plain run never reuses tsgo's build info.
• A solution-style tsconfig is checked as written: a root that only
  lists references is no longer redirected into its sub-projects;
  svelte-check compiles nothing there and reports only Svelte warnings.

v1.6.0

Compare Source

A parity release built from an audit of every place the emit, analyze
and lint crates still read JavaScript or TypeScript by scanning bytes
instead of parsing it. Two user-reported regressions (#​56, #​57) came
from that class of code; the audit found twenty-five more sites, each
was compared with the upstream svelte2tsx source that makes the same
decision, and every one now goes through the parser. Three compiler
errors svelte-check reports were also never produced here; they are
now. Both control workspaces report identical diagnostics before and
after.

Fixed

• A $: statement no longer breaks the render function (#​56, #​57).
  $: ({ a, b } = obj) and $: x = y, z were rewritten by a byte
  scanner that split on the wrong comma or parenthesis, producing a
  file tsgo could not parse — and a parse failure hides every other
  error in that file. The reactive rewrite now runs on the statement's
  AST.
• Generated TypeScript that failed to parse for api.void(1, 2)
  (a method named void), $$Generic<Record<string, () => void>>,
  generics="T extends 'a,b', U" and {@debug a // note, y}. Each
  hid the whole file's diagnostics.
• Errors that diverged from upstream for: $count after a regex
  literal containing a quote; type A = $$Generic; inside a comment;
  generics="T extends () => void, U" (the second parameter was
  dropped); $$Generic<{ a: string, b: number }>; each / snippet /
  then / catch patterns with quoted keys, string defaults, => in a
  type or a computed key; SvelteKit load() with an unrelated JSDoc
  block earlier in the file; /* @ts-ignore */ above an import;
  bind:value={/* c */ rest.b}; {#each f("(")(")") as row}; string
  literals containing from "../…" being rewritten on disk; void (a, b) outside a $: statement.
• Runes mode is decided the way the compiler decides it: a rune
  name in markup or a comment, or $inspect alone, no longer switches
  it on; $state.raw<T>(), template declaration tags and top-level
  await do.
• bind:this targets keep their declaration as written. A direct
  read before the element mounts reports TS2454 as upstream does;
  reads inside closures stay clean. Bindings with no element-side type
  (bind:innerWidth on <svelte:window>) count as assigned.
• Runes mode is a strict-events trigger only on the generics export
  path, as in upstream: a runes child with an untyped dispatcher
  accepts $on of any name.
• The compiler's global_reference_invalid, bind_invalid_name and
  bind_invalid_target errors are reported, with upstream's
  semantics: the first compiler error in a file is the only error for
  that file and replaces its warnings. bind_invalid_name carries the
  compiler's "Did you mean" suggestion. A top-level $: x = …
  declares x, so $x is a store subscription rather than an illegal
  global.
• An unknown bind:NAME on a DOM element is passed as an attribute
  ("bind:NAME": expr), so the element's attribute type reports it
  (TS2353) at the column upstream anchors to.
• $store subscriptions are declared where upstream declares them:
  ;let $store = __svn_store_get(store); right after the store's own
  declaration (module scope for module-script stores, the start of the
  render function for imports), inside ignore comments. A $name
  whose name is not a store is any, as upstream, instead of the
  binding's own type; a self-referencing subscription (const derived = $derived.by(...)) reports the same TS2448 upstream does.
• SvelteKit: export const GET = (event) => … on a +server gets
  its RequestEvent / Response annotations; a +page.js in a
  project without allowJs no longer makes the compiler abandon the
  program and report 0 errors.
• Unused-name reports match upstream. The template no longer emits
  a void NAME; per identifier a tokenizer found in markup, which hid
  unused-variable reports on object keys, regex bodies, private names,
  type-only imports and write-only bind targets; a type alias sharing
  a body const's name stays in the render function so the merged
  symbol counts as read.
• Each and await bindings resolve at value level
  (__svn_unwrap_arr(items) / __svn_unwrap_promise_like(p)) instead
  of from a type derived from the items text, which picked the wrong
  filter overload and collapsed list ?? [] to any.
• A bind:value expression is read before it is assigned, and a
  catch-only {#await} still awaits its promise (both upstream
  shapes).
• Files with a pug template no longer report unused-name
  diagnostics.

Changed

• MSRV 1.95 → 1.96. Required by oxc 0.148, which needs Rust 1.96.
  rust-toolchain.toml moves to 1.96 with it, and the whole lockfile
  is refreshed. oxc 0.144 → 0.148 brings only parser bug fixes for the
  crates we use (stricter rejection of malformed input, a panic fix on
  escaped string export names).
• The shim's fallback svelte/elements (used only when no svelte
  is installed) lists the bind: keys real svelte declares instead
  of accepting any bind:* key.
• The diagnostic mapper is exposed for callers that run tsgo
  themselves.

Internal

• One AST runes probe (svn_analyze::RunesProbe) is shared by emit,
  the props synthesiser and lint; oxc_ast_visit visitors replace
  every hand-written scanner, and the redundant text helpers were
  deleted. The v5-stores suite now requires all 24 fixtures to match
  their upstream-locked lists.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	wxcn	d09a1eb	Sep 21 2026, 11:41 PM

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	svelte-check-native@​1.5.2 ⏵ 1.8.0	+4		+1

View full report