rspack-v2-upgrade_skill

This skill helps upgrade a Rspack 1.x project to v2 by guiding dependency updates, config changes, and validation against the official migration guide.

JavaScript

36

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill rstackjs/agent-skills --skill rspack-v2-upgrade

SKILL.md1.2 KB

Overview

This skill guides upgrading a Rspack 1.x project to Rspack v2, covering dependency changes and configuration updates. It consolidates the migration workflow, points to the official migration guide as the source of truth, and helps validate the result with build and test checks. Use it to reduce upgrade risk and uncover breaking changes early.

How this skill works

The skill inspects package.json and locates the project Rspack configuration file (rspack.config.(ts|js|mjs|cjs)). It compares current config and plugins against the official Rspack v2 migration notes, recommends dependency updates for @rspack/core, @rspack/cli and @rspack/dev-server, and produces a checklist of required config edits. Finally, it guides running builds, dev server, and tests to validate the migration and surface remaining issues.

When to use it

Preparing to move a project from Rspack 1.x to Rspack v2 (beta).
After discovering build or dev-server incompatibilities following a library update.
When auditing config for deprecated or renamed Rspack options and plugins.
Before upgrading dependencies in CI to avoid breaking the main branch.
When setting a migration plan for multiple repositories or a monorepo.

Best practices

Treat the official migration guide as the single source of truth and follow it step‑by‑step.
Start by reading package.json and locating rspack.config.* to scope required changes.
List and prioritize breaking changes that affect your project, then update dependencies before code edits.
Run incremental builds and tests after each change to catch regressions early.
Keep a concise changelog of removed/renamed options and plugin API adjustments for the team.

Example use cases

Upgrading a single-page app that uses custom Rspack plugins and needs config renames applied.
Migrating a component library in a monorepo where multiple packages reference @rspack/core.
Updating CI pipelines to install @rspack/core@beta and validating that builds still pass.
Converting a legacy rspack.config.ts to the v2 configuration shape and removing deprecated options.
Troubleshooting dev-server startup failures after bumping Rspack packages.

FAQ

Update core packages together (@rspack/core, @rspack/cli, @rspack/dev-server) to match v2; staggered updates can cause incompatibilities.

Where should I look for breaking change details?

Use the official Rspack v2 migration guide as the definitive reference and compare your current config to the examples there.