upgrade-svelte

Upgrades the Svelte submodule, regenerates fixtures, and fixes compiler regressions until tests pass.

218|11|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/baseballyama/rsvelte --skill upgrade-svelte-baseballyama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upgrade-svelte
Source: https://github.com/baseballyama/rsvelte/tree/main/.claude/skills/upgrade-svelte
Command: npx skills add https://github.com/baseballyama/rsvelte --skill upgrade-svelte-baseballyama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a Rust port of the Svelte 5 compiler in sync with upstream releases is tedious: each new Svelte version can change AST nodes, codegen output, compiler options, and error codes, silently breaking compatibility. This Skill automates the upgrade and drives a structured fix loop until the compatibility report reaches 100%. ## Core Features & Use Cases - Automated Upgrade Pipeline: Checks out the target svelte@ tag, builds the upstream compiler, regenerates fixtures, and refreshes docs via the upgrade script. - Failure Triage: Parses the compatibility report JSON and groups failures by cause (parser, codegen, validator, CSS, SSR, runtime) with a defined fix order. - Guided Regression Fixing: Maps upstream compiler phases to mirrored Rust modules so each fix follows the reference implementation, with per-fix commits and clippy/fmt gates. - Use Case: After Svelte 5.52.0 ships with new warning codes, run the Skill to upgrade the submodule, identify the failing validator tests, port the new warnings into the Rust error module, and ship with a 100% compatibility report. ## Quick Start Ask the agent to upgrade the Svelte submodule to the latest version and fix all regressions until the compatibility report passes.

Frequently Asked Questions about upgrade-svelte

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade the Svelte submodule to a specific version?▼

Pass the version as an argument, for example 5.52.0, or omit it to use the latest stable svelte@ tag. The upgrade script checks out the tag, builds the upstream compiler with pnpm, regenerates fixtures, and produces a compatibility report.

How do I fix Svelte compiler test failures after an upgrade?▼

Read the compatibility report JSON, group failures by cause, then fix in order: parser, compiler errors, validator warnings, CSS, SSR, snapshots, runtime. Mirror the upstream implementation in the corresponding Rust phase module and commit each fix separately.

Why does the pnpm build step fail during the Svelte upgrade?▼

The upstream compiler's compiler/index.js is gitignored, so pnpm install and pnpm build inside submodules/svelte/packages/svelte are mandatory. Check that Node is version 22 or newer and try pnpm install --no-frozen-lockfile if installation fails.

What counts as a successful Svelte upgrade in this workflow?▼

The compatibility report must show zero failures and zero errors in every category, cargo test --release must pass, and docs must be regenerated with update-docs. The final commit records the version bump, fixture regeneration, and fixed regressions.

Where do new Svelte compiler features get implemented in the Rust port?▼

New AST nodes go in crates/rsvelte_core/src/ast/template.rs, then flow through the mirrored phases 1_parse, 2_analyze, and 3_transform client/server modules. New error and warning codes go in crates/rsvelte_core/src/error/.