migrate-to-rspacklisted

Use when migrating an existing Meteor 3 app to the Rspack bundler integration (`rspack` Atmosphere package, Meteor 3.4+). Triggers on removing nested imports, defining mainModule entry points, server-only apps, replacing fourseven:scss / meteor/less / coffeescript / jorgenvatle:vite / zodern:melte build plugins with Rspack loaders, "Error: 'import' and 'export' cannot be used outside of module code", CommonJS default-import interop, _build / build-assets / build-chunks folders, module.exports in a client graph, Node built-ins in browser code, .meteorignore hiding mainModule handoff files, dynamic chunks under ROOT_URL, meteor.modules for CSS or HTML, resolve.symlinks in a monorepo, resolve.alias migration, meteor update --npm in CI/Docker. Use this skill when the user asks about converting an app to Rspack, asks about a build plugin's Rspack replacement, or asks about CI/Docker errors after upgrading. For setup and rspack.config.js helpers, use meteor-modern-build-stack instead.
meteor/agent-skills · ★ 7 · Web & Frontend · score 74

Install: claude install-skill meteor/agent-skills

# Migrate an existing app to Rspack Rspack compiles app code while Meteor builds Atmosphere packages and assembles the final bundle. Do not rewrite packages merely because Rspack is enabled, but audit their architecture declarations and browser-incompatible dependencies. Prerequisite: Meteor 3.4+. Strongly recommended to enable `"meteor": { "modern": true }` first (Meteor 3.3+) and fix Babel fallbacks, then add Rspack. See the `meteor-modern-build-stack` skill for the activation knobs and `rspack.config.js` shape. Match `@meteorjs/rspack` to the Meteor release, not to `@rspack/core` or `@rspack/cli`: | Meteor | `rspack` | `@meteorjs/rspack` | Capability boundary | |---|---|---|---| | 3.4 | `1.0.0` | `1.0.0` | Base integration and helpers. | | 3.4.1 and 3.5 | `1.1.0` | `2.0.1` | Adds v2 helpers and inherited `TOOL_NODE_FLAGS`. | | 3.5.1 | `1.2.0` | `2.1.0` | Revised client polyfills and extension discovery. | | 3.5.2 | `1.3.0` | `2.2.0` | Dependency diagnostics, mode isolation, full-app/TLA and cache fixes. | The Atmosphere, Meteor npm integration, and Rspack core package versions are independent. Inspect `.meteor/versions`, `package.json`, and the lockfile. After changing the Meteor release, run `meteor update --npm`, inspect the npm changes, and commit the dependency files. Do not pair a newer integration major with an older Meteor release only to copy a current helper. ## Decision flow 1. Does the app define client and server entry points in `package.json` `meteor