rspack-v2-upgrade
Skill97 starsChanged 3 months agoMITView on GitHub
Use when upgrading a Rspack 1.x project to v2, including dependency and configuration updates.
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Read package.json to identify Rspack packages in use.
- Distinctive: line 15
Use the official guide as the single source of truth:
- Distinctive: line 27
Update the Rspack config and related code according to the official guide.
- Distinctive: line 28
Remove deprecated or unsupported options.
- Distinctive: line 31
Run build and dev commands.
- Distinctive: line 32
Run project tests or type checks.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Rspack 1.x to v2 upgrade
Workflow
- Confirm current setup
- Read
package.jsonto identify Rspack packages in use. - Locate the Rspack config file (commonly
rspack.config.(ts|js|mjs|cjs)).
- Read
- Open the official migration guide
- Use the official guide as the single source of truth:
- Plan required changes
- Compare the current project config with the migration guide.
- List breaking changes that apply to the project’s current config and plugins.
- Note any removed or renamed options, defaults, or plugin APIs.
- Update dependencies
- Upgrade Rspack packages to v2:
@rspack/core,@rspack/cli,@rspack/dev-server,@rspack/plugin-react-refresh.
- Upgrade Rspack packages to v2:
- Apply migration changes
- Update the Rspack config and related code according to the official guide.
- Remove deprecated or unsupported options.
- Validate
- Run build and dev commands.
- Run project tests or type checks.
- Fix any warnings or errors surfaced by the new version.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- create-draft-release-notesSkill
- mdx-to-markdownSkill
- pr-creatorSkill
- release-blog-writerSkill
- rstack-docs-writerSkill
- rstack-eco-ci-debugSkill
- rstack-repo-maintainSkill
- rstack-skill-evaluatorSkill
- migrate-to-rsbuildSkill
- migrate-to-rslibSkill
- migrate-to-rslintSkill
- migrate-to-rstestSkill
- rsbuild-best-practicesSkill
- rsbuild-v2-upgradeSkill
- rsdoctor-analysisSkill
- rsdoctor-v2-upgradeSkill
- rslib-best-practicesSkill
- rslib-modern-packageSkill
- rspack-best-practicesSkill
- rspack-debuggingSkill
- rspack-split-chunksSkill
- rspack-tracingSkill
- rspress-best-practicesSkill
- rspress-custom-themeSkill
- rspress-description-generatorSkill
- rspress-docs-generatorSkill
- rspress-v2-upgradeSkill
- rstest-best-practicesSkill
- rstest-debuggingSkill
- storybook-rsbuildSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.