feat(rspack): support @rspack/core@2 and @rsbuild/core@2 (multi-version compliance) by FrozenPandaz · Pull Request #35682 · nrwl/nx

FrozenPandaz · 2026-05-14T03:31:18Z

Summary

Adds support for @rspack/core@2 and @rsbuild/core@2 across @nx/rspack, @nx/rsbuild, @nx/angular-rspack, and @nx/module-federation. v1 stays in the supported window (multi-version policy: latest + previous major).

Catalog now resolves to @rspack/[email protected] / @rsbuild/[email protected].
Version maps + detection utilities pick v1 or v2 based on the installed major.
New packageJsonUpdates migrations move workspaces still on @rspack/core@^1 / @rsbuild/core@^1 to v2 (23.0.0-beta.20, gated by requires).

v2 breaking changes and how each is handled

1. `@rspack/core@2` is pure ESM at the entry, but the bundle is CJS

A direct top-level import from @rspack/core no longer works in places where Nx loads its own plugin modules synchronously. The CJS dist/index.js is what actually resolves under require().

Addressed: lazy-load @rspack/core where Nx eagerly imported it, so the import is deferred until the consuming code actually runs. See feat(rspack): load @rspack/core lazily for v2 esm compatibility.

2. `@rspack/dev-server@2` is a ground-up rewrite — no longer wraps `webpack-dev-server`

v1's @rspack/dev-server depended on webpack-dev-server, whose Server.js sets process.env.WEBPACK_SERVE = 'true' at module load. v2 dropped that dependency entirely; the env var is never set. The rspack 2 CLI signals serve mode via
setBuiltinEnvArg(env, 'SERVE', true) → RSPACK_SERVE on the config-function env arg, not process.env.

Every process.env['WEBPACK_SERVE'] check across @nx/rspack, @nx/angular-rspack, and @nx/module-federation would silently fall through to build mode on rspack 2.

Addressed by three bridges — one per config-shape:

composePlugins-based configs (most @nx/rspack user configs): bridge in composePlugins.combined reads ctx['env']['RSPACK_SERVE'] and sets process.env.WEBPACK_SERVE. See fix(rspack): bridge rspack 2 RSPACK_SERVE to WEBPACK_SERVE.
createConfig-based configs (@nx/angular-rspack export default createConfig(...)): rspack never passes env to value exports, so the env-arg bridge can't run. argv-based detection inside createConfig (process.argv[2] ∈ {serve, server, s, dev}) instead. See fix(angular-rspack): bridge rspack 2 serve signal via argv detection.
Plain-object configs (@nx/react:host generated rspack.config.ts is an object literal, not a function): neither bridge above runs. Shared bridgeRspackServeEnv() helper called at the top of each MF dev-server plugin's apply(). See
fix(module-federation): bridge rspack 2 serve signal in dev-server plugins.

3. Tightened `RuleSetRule` typings broke flattened `oneOf` shapes

The v2 type refactor revealed that rules: [{ oneOf: [...] }, { use }] (master) and oneOf: [..., { use }] (the simplification attempt) are not equivalent. Flat oneOf picks a single matching branch — language loaders left as a sibling use
got dropped for tagged style files.

Addressed: concatenate language loaders into each oneOf branch in style-config-utils.ts so tagged files still preprocess. See fix(angular-rspack): apply language loaders to tagged style files.

4. `experiments.outputModule` no longer accepted in the same shape

Setting experiments.outputModule: true is a v1 idiom; on v2 it surfaces as a warning/typing issue depending on the context.

Addressed: only set it on v1, omit on v2. See fix(angular-rspack): omit experiments.outputModule on rspack v2 and fix(module-federation): only set experiments.outputModule on rspack v1.

5. `stats.profile` / `statsJson` no longer accept the v1 shape

The v1 profile/stats notices fired on v2 spuriously.

Addressed: drop the v1-only branch on v2, keep an informational notice for plugin authors. See fix(angular-rspack): drop the v2 statsJson notice, fix(rspack): drop the v2 statsJson profile warning.

6. `afterDone` may fire with `undefined` stats on error

v2 propagates compilation errors via the run callback before afterDone resolves; the hook is still called but stats is undefined, masking the real error.

Addressed: guard with if (!stats) return;. See fix(angular-rspack): guard afterDone handler against undefined stats.

7. `--watch` flag rename in `@rsbuild/core@2`

The plugin snapshot diverged from the renamed flag.

Addressed: sync snapshot. See fix(rsbuild): sync plugin snapshot to renamed watch flag.

8. Peer-dep auto-install picks first satisfiable sub-range

@nx/angular-rspack's peer was >=1.3.5 <1.7.0 || ^2.0.0. pnpm's auto-install-peers resolves multi-major OR ranges against the first satisfiable sub-range, so v2 catalogs were ending up with stray @rspack/[email protected].

Addressed: reverse to ^2.0.0 || >=1.3.5 <1.7.0. Empirically verified the v1 sub-range no longer steals resolution. See fix(angular-rspack): order @rspack/core peer range v2-first.

9. Migrations + v1→v2 `packageJsonUpdates`

packages/rspack/migrations.json: new 23.0.0-rspack-v2 packageJsonUpdates entry (gated by requires: { "@rspack/core": ">=1.0.0 <2.0.0" }) bumps @rspack/core + siblings to ^2.0.4. Plus requires gates added to existing
module-federation migrations (21.3.0, 22.2.0).
packages/rsbuild/migrations.json: new 23.0.0-rsbuild-v2 packageJsonUpdates entry (gated similarly) bumps to ^2.0.7.
All entries pinned to 23.0.0-beta.20.

10. Docs

Supported-versions windows widened to include v2 in both rspack and rsbuild docs pages.

Known limitation: `rspack serve` under Cypress 15

The should have interop between rspack host and webpack remote case in e2e/react/src/module-federation/misc-rspack-interoperability.test.ts (re-enabled in master via #35764) hits an upstream incompatibility when an rspack 2 dev server
is launched under Cypress 15's e2e runner:

> rspack serve --port=6104 --node-env=development
[rspack-cli] TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
    at join (node:path:1339:7)
    at key (.../@rspack/core/dist/index.js:2549:167)        ← LOADER_PATH = join(import.meta.dirname, 'cssExtractLoader.js')
    at Object.<anonymous> (.../@rspack/core/dist/index.js:13607:16)
    at Module._compile (.../cjs/loader:1760:14)
    at Object.transformer (.../Cypress/15.15.0/.../tsx/dist/register-D46fvsV_.cjs:3:1104)

Root cause (three layers):

@rspack/core@2 ships import.meta.dirname in its CJS bundle (dist/index.js, lines 2549 + 3462) without a __dirname fallback.
Cypress 15.x bundles [email protected] inside the Electron app and registers it as a global CJS require-hook. The subprocess spawned for nx run shell:serve inherits this via NODE_OPTIONS.
[email protected] doesn't synthesize import.meta.dirname when transforming CJS, so the value is undefined and path.join(undefined, …) throws.

Upstream status:

rspack #13420 — closed as not-rspack's-bug; maintainer points to tsx.
tsx #781 — fixed in tsx 4.22.0 (released 2026-05-14).
Cypress 15.15.0 (current latest) still bundles tsx 4.20.6 — waiting on Cypress to bump bundled tsx ≥ 4.22.0.

Scope: only the rspack host branch of the interop test trips it. webpack host + rspack remote passes (no rspack serve under Cypress).

Decision: leave the test as-is, do not skip — once Cypress ships with bundled tsx ≥ 4.22.0, the failure clears on its own.

Test Plan

nx run-many -t test,build,lint -p rspack,rsbuild,angular-rspack,module-federation
nx affected -t build,test,lint
nx affected -t e2e-local (see Known limitation above)
Manual smoke: scaffold workspaces against @rspack/core@^1, ^2, @rsbuild/core@^1, ^2. Init + build + serve. Confirm no version overwrite.

Fixes NXC-4460

netlify · 2026-05-14T03:31:25Z

✅ Deploy Preview for nx-dev ready!

Name	Link
🔨 Latest commit	`8c04f14`
🔍 Latest deploy log	https://app.netlify.com/projects/nx-dev/deploys/6a32e4130c89f600088f3704
😎 Deploy Preview	https://deploy-preview-35682--nx-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

netlify · 2026-05-14T03:31:25Z

✅ Deploy Preview for nx-docs ready!

Name	Link
🔨 Latest commit	`8c04f14`
🔍 Latest deploy log	https://app.netlify.com/projects/nx-docs/deploys/6a32e41318edab00094ea9ea
😎 Deploy Preview	https://deploy-preview-35682--nx-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

nx-cloud · 2026-05-14T03:31:58Z

View your CI Pipeline Execution ↗ for commit 8c04f14

Command	Status	Duration	Result
`nx affected --targets=lint,test,build,e2e,e2e-c...`	✅ Succeeded	16m 45s	View ↗
`nx run-many -t check-imports check-lock-files c...`	✅ Succeeded	5s	View ↗
`nx-cloud record -- pnpm nx-cloud conformance:check`	✅ Succeeded	1m 2s	View ↗
`nx build workspace-plugin`	✅ Succeeded	<1s	View ↗
`nx-cloud record -- nx sync:check`	✅ Succeeded	20s	View ↗
`nx-cloud record -- nx format:check`	✅ Succeeded	10s	View ↗

☁️ Nx Cloud last updated this comment at 2026-06-17 20:37:54 UTC

socket-security · 2026-05-15T15:39:01Z

All alerts resolved. Learn more about Socket for GitHub.

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report

nx-cloud

Important

At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.

Nx Cloud is proposing a fix for your failed CI:

We add a null guard at the top of the compiler.hooks.afterDone tap callback in AngularRspackPlugin so that rspackStatsLogger is never invoked with an undefined stats argument. In @rspack/core v2 the afterDone hook can fire without a stats object when a compilation terminates in an error path before stats are generated, which was the direct cause of the TypeError: Cannot read properties of undefined (reading 'toJson') crash seen across all 13 examples-angular-rspack-*:build tasks. Both the TypeScript source and the compiled dist file are patched so the fix takes effect immediately regardless of cache state.

Note

⏳ We are verifying this fix by re-running a subset of the 19 failed tasks that were analyzed.

diff --git a/packages/angular-rspack/src/lib/plugins/angular-rspack-plugin.ts b/packages/angular-rspack/src/lib/plugins/angular-rspack-plugin.ts
index a98ea014..c984c436 100644
--- a/packages/angular-rspack/src/lib/plugins/angular-rspack-plugin.ts
+++ b/packages/angular-rspack/src/lib/plugins/angular-rspack-plugin.ts
@@ -325,6 +325,11 @@ export class AngularRspackPlugin implements RspackPluginInstance {
     });
 
     compiler.hooks.afterDone.tap(PLUGIN_NAME, (stats) => {
+      // In @rspack/core v2, afterDone may fire with undefined stats when a
+      // compilation terminates in an error path before stats are generated.
+      if (!stats) {
+        return;
+      }
       // Get stats options - merge defaults with user's config if provided
       const configStats = compiler.options.stats;
       const defaultStatsOptions = getStatsOptions(this.#_options.verbose);

Or Apply changes locally with:

npx nx-cloud apply-locally XFa0-Pf0N

Apply fix locally with your editor ↗ View interactive diff ↗

_{🎓 Learn more about Self-Healing CI on nx.dev}

socket-security · 2026-06-11T19:09:47Z

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/@rspack/core@2.0.8
	npm/cypress@15.17.0
	npm/@rspack/cli@2.0.8
	npm/ts-checker-rspack-plugin@1.4.0
	npm/@rspack/plugin-react-refresh@2.0.2
	npm/@rspack/dev-server@2.0.3

View full report

Cypress 15.x bundled tsx 4.20.6 which did not synthesize import.meta.dirname, breaking @rspack/core@2 (which uses it in its CJS bundle) when run under Cypress's tsx require-hook. 15.17.0 ships tsx 4.22.4, which restores the synthesis. Adds a 23.0.0-beta.26 packageJsonUpdates entry so workspaces on cypress <15.17.0 pick up the fix on migrate. Exempts cypress from the minimumReleaseAge guard so the bump can land before the 24h supply-chain cooldown elapses.

Aligns the v1->v2 packageJsonUpdates and module-federation gated entries to the current 23.0.0 beta cut so they ship in the same release window. Also bumps the rsbuild migrations to keep the v2 transition aligned.

Replace the six inline process.env['WEBPACK_SERVE'] reads with isServeMode() from a new rspack-serve-env util. The util also exports bridgeRspackServeEnv(), which createConfig calls to keep cross-package consumers (generated rspack configs, module-federation plugins) working on rspack 2. isServeMode falls back to argv when the env var is unset, so AngularRspackPlugin instantiated outside createConfig also reports serve mode correctly.

@rspack/dev-server v2 sets process.env.RSPACK_SERVE at module load, just like v1's webpack-dev-server set WEBPACK_SERVE. rspack-cli imports @rspack/dev-server before invoking the config loader for the serve and preview commands, so the env var is reliably present by the time createConfig runs. Check it directly instead of sniffing process.argv, and drop the bridge helper — every angular-rspack call site now uses isServeMode().

Replace the eleven inline process.env['WEBPACK_SERVE'] reads across the angular/rspack/webpack dev-server plugins and with-module-federation helpers with a shared isServeMode() util that checks both WEBPACK_SERVE (v1) and RSPACK_SERVE (v2). @rspack/dev-server v2 sets RSPACK_SERVE on module load, and rspack-cli imports it before loading the user config, so the env var is available without any argv sniff or bridge step. Delete bridge-rspack-serve-env now that no caller needs the WEBPACK_SERVE variable specifically.

… builds Trim the multi-line v1/v2 explainers, redundant docstrings, and codepath- restatement comments added during the rspack 2 work down to the essential WHY. Drop the WEBPACK_SERVE='false' override in build-static-remotes — the string 'false' is truthy so it never disabled serve detection; delete both WEBPACK_SERVE and RSPACK_SERVE from the spawn env via the new childBuildEnv() helper so the child build doesn't masquerade as a serve.

…ins bridge Replace the two inline process.env['WEBPACK_SERVE'] reads in apply-base-config with isServeMode(), which also accepts RSPACK_SERVE (v2's signal). With those reads gone, the composePlugins bridge that synced ctx.env.RSPACK_SERVE to process.env.WEBPACK_SERVE has no remaining consumer — rspack-cli's serve command already imports @rspack/dev-server (which sets process.env.RSPACK_SERVE) before invoking the config loader. Drop the bridge.

rspack 1.x's ProgressPlugin wrapper spreads its third callback arg (progress(p, msg, ...items)) and crashes when the native binding passes undefined. Fixed upstream only in rspack 2.x. Tap compile/invalid/done compiler hooks directly instead of extending the built-in plugin.

… compiler The static @rspack/core import can be a different major than the rspack actually running the build (e.g. repo dist on v1 driving an app on v2). getCompilationHooks rejects Compilation instances from a foreign copy, so pull the javascript namespace off compiler.rspack instead.

… compiler [Self-Healing CI Rerun]

[email protected] is past the 24h release-age window; the temporary exclusion is no longer needed.

@rspack/plugin-react-refresh@2 is pure ESM and only exports the named ReactRefreshRspackPlugin; require(esm) returns a namespace with no default, so 'mod.default ?? mod' produced a non-constructor and every react dev-serve crashed with 'ReactRefreshPlugin is not a constructor'.

… apps rspack-cli@2 dev mode auto-enables lazyCompilation { imports: true } unless the exported config sets it explicitly. The lazy-compilation proxy wraps the import('./bootstrap') entry of federated apps and its update chunk 404s under the MF dev-server, so remotes render a blank page. Set lazyCompilation: false in the generated MF rspack configs, default it in withModuleFederation, and insert it into existing MF configs via the v2 config migration.

… apps [Self-Healing CI Rerun]

@rspack/dev-server@2 prints 'Local:' where v1 printed 'Loopback:', so the serve-readiness check timed out even though the server was up.

The old WEBPACK_SERVE: 'false' override was a truthy string, so static remote child builds always ran with a serve signal and angular-rspack picked its development configuration. Removing the override flipped them to production, where default Angular bundle budgets fail freshly generated apps. Signal the intent explicitly via NGRS_CONFIG=development (respecting a user-provided value).

nx checks a migration requires range against the version the package is bumped TO. The config-rewrite migrations were gated >=1.0.0 <2.0.0, so the v2 bump failed the gate and the migrations were skipped. Gate on >=2.0.0 so they run when the user lands on v2, matching the vite/vitest convention. Also retarget the rspack v2 migration entries to 23.1.0-beta.0.

Same fix as rspack: gate the config-rewrite migrations on >=2.0.0 instead of >=1.0.0 <2.0.0 so they run when the user upgrades to rsbuild v2 rather than being skipped. Also retarget the rsbuild v2 migration entries to 23.1.0-beta.0.

Move the cypress 15.17 packageJsonUpdate from 23.0.0-beta.26 to 23.1.0-beta.0 alongside the rspack/rsbuild v2 migrations.

The rspack-version helper used a top-level value import of @rspack/core, re-introducing the eager load the rest of the change avoids and pulling it back transitively through common-config and browser-config. These call sites run at config-build time, before a compiler exists, so defer the read with a lazy require, matching apply-base-config.

The async conversion was leftover from an abandoned await import() approach; the helper bodies do no async work. Returning a Promise gratuitously widened the contract of these deprecated helpers. Revert to sync; the executor already awaits and composePlugins handles sync plugins, so behavior is unchanged.

…eywords (#36326) ## Current Behavior `nx release changelog` extracts issue references from the commit body with a bare `/(#\d+)/gm` regex, so **every** `#number` in a squashed PR description becomes an issue link in the changelog — including other repos' issue numbers. For example, the [23.1.0 release notes](https://github.com/nrwl/nx/releases/tag/23.1.0) contain: > **rspack:** support @rspack/core@2 and @rsbuild/core@2 (multi-version compliance) (#35682, #35764, #13420, #781) where `#13420` is actually `web-infra-dev/rspack#13420` and `#781` is `privatenumber/tsx#781` — upstream issues discussed in the PR description, rendered as (bogus) `nrwl/nx` issue links. The same release also picked up `nrwl/nx-console#3175`, `react/react#418`, and `web-infra-dev/rspack#2292`, plus noisy same-repo PR mentions that were merely referenced in prose. ## Expected Behavior Issue references are only extracted from the commit body when linked via a GitHub closing keyword (`Fixes #123`, `Closes #123`, `Resolves: #123`, ...) — the same rule GitHub itself uses to auto-link and close issues. Cross-repo forms (`owner/repo#123`), markdown links to other repos, and casual same-repo mentions no longer produce changelog references. Subject-line extraction (the PR number in `(#123)` and inline issue refs) is unchanged. Both regular commits and version plans go through the same `extractReferencesFromCommit` function, so this fixes both paths. ## Related Issue(s) N/A  --- [View session information ↗](https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/Fix-nx-release-changelog-scraping-other-repos-issue-numbers-7967dd62)

…eywords (#36326) ## Current Behavior `nx release changelog` extracts issue references from the commit body with a bare `/(#\d+)/gm` regex, so **every** `#number` in a squashed PR description becomes an issue link in the changelog — including other repos' issue numbers. For example, the [23.1.0 release notes](https://github.com/nrwl/nx/releases/tag/23.1.0) contain: > **rspack:** support @rspack/core@2 and @rsbuild/core@2 (multi-version compliance) (#35682, #35764, #13420, #781) where `#13420` is actually `web-infra-dev/rspack#13420` and `#781` is `privatenumber/tsx#781` — upstream issues discussed in the PR description, rendered as (bogus) `nrwl/nx` issue links. The same release also picked up `nrwl/nx-console#3175`, `react/react#418`, and `web-infra-dev/rspack#2292`, plus noisy same-repo PR mentions that were merely referenced in prose. ## Expected Behavior Issue references are only extracted from the commit body when linked via a GitHub closing keyword (`Fixes #123`, `Closes #123`, `Resolves: #123`, ...) — the same rule GitHub itself uses to auto-link and close issues. Cross-repo forms (`owner/repo#123`), markdown links to other repos, and casual same-repo mentions no longer produce changelog references. Subject-line extraction (the PR number in `(#123)` and inline issue refs) is unchanged. Both regular commits and version plans go through the same `extractReferencesFromCommit` function, so this fixes both paths. ## Related Issue(s) N/A  --- [View session information ↗](https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/Fix-nx-release-changelog-scraping-other-repos-issue-numbers-7967dd62)  (cherry picked from commit d7312d2)

This comment was marked as outdated.

Sign in to view

FrozenPandaz force-pushed the feature/nxc-4460-rspack-rsbuild-v2-support branch 4 times, most recently from 329a4d1 to 8ea2d24 Compare May 15, 2026 15:37

FrozenPandaz force-pushed the feature/nxc-4460-rspack-rsbuild-v2-support branch 2 times, most recently from 8cad94e to ca11bc6 Compare May 15, 2026 20:16

FrozenPandaz marked this pull request as ready for review May 15, 2026 22:38

FrozenPandaz requested a review from a team as a code owner May 15, 2026 22:38

FrozenPandaz requested a review from AgentEnder May 15, 2026 22:38

FrozenPandaz force-pushed the feature/nxc-4460-rspack-rsbuild-v2-support branch from 65949fc to 11d4251 Compare May 15, 2026 22:58

nx-cloud Bot reviewed May 15, 2026

View reviewed changes

FrozenPandaz force-pushed the feature/nxc-4460-rspack-rsbuild-v2-support branch 3 times, most recently from cbfb651 to 18b2714 Compare May 22, 2026 13:51

FrozenPandaz marked this pull request as draft May 22, 2026 20:11

FrozenPandaz force-pushed the feature/nxc-4460-rspack-rsbuild-v2-support branch from 10533f2 to 2da1a30 Compare May 22, 2026 20:13

nachocodoner mentioned this pull request May 26, 2026

Support Rspack 2.x meteor/meteor#14360

Open

FrozenPandaz force-pushed the feature/nxc-4460-rspack-rsbuild-v2-support branch 5 times, most recently from dd8d4a5 to 6f17e62 Compare June 11, 2026 14:43

FrozenPandaz force-pushed the feature/nxc-4460-rspack-rsbuild-v2-support branch 2 times, most recently from 26aeff8 to c16b92c Compare June 16, 2026 19:32

FrozenPandaz and others added 23 commits June 17, 2026 14:04

chore(rspack): bump v2 migrations to 23.0.0-beta.20

0cb6b70

chore(rspack): bump migration target from beta.20 to beta.26

81c4dd2

Aligns the v1->v2 packageJsonUpdates and module-federation gated entries to the current 23.0.0 beta cut so they ship in the same release window. Also bumps the rsbuild migrations to keep the v2 transition aligned.

fix(angular-rspack): resolve JavascriptModulesPlugin from the running…

ed54b14

… compiler [Self-Healing CI Rerun]

chore(repo): drop cypress from minimumReleaseAgeExclude

9588493

[email protected] is past the 24h release-age window; the temporary exclusion is no longer needed.

fix(module-federation): disable rspack lazy compilation for federated…

7722a5a

… apps [Self-Healing CI Rerun]

fix(rspack): match rspack dev-server v2 'Local:' output in mf e2e

ae67b52

@rspack/dev-server@2 prints 'Local:' where v1 printed 'Loopback:', so the serve-readiness check timed out even though the server was up.

chore(repo): update lockfile for rspack and rsbuild v2

1916be4

chore(testing): retarget cypress 15.17 migration to 23.1.0-beta.0

594711e

Move the cypress 15.17 packageJsonUpdate from 23.0.0-beta.26 to 23.1.0-beta.0 alongside the rspack/rsbuild v2 migrations.

FrozenPandaz force-pushed the feature/nxc-4460-rspack-rsbuild-v2-support branch from d0a22de to 8c04f14 Compare June 17, 2026 18:14

FrozenPandaz merged commit 668c1cb into master Jun 17, 2026
28 of 30 checks passed

FrozenPandaz deleted the feature/nxc-4460-rspack-rsbuild-v2-support branch June 17, 2026 20:54

FrozenPandaz mentioned this pull request Jul 13, 2026

fix(release): only extract body issue references linked via closing keywords #36326

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(rspack): support @rspack/core@2 and @rsbuild/core@2 (multi-version compliance)#35682

feat(rspack): support @rspack/core@2 and @rsbuild/core@2 (multi-version compliance)#35682
FrozenPandaz merged 56 commits into
masterfrom
feature/nxc-4460-rspack-rsbuild-v2-support

FrozenPandaz commented May 14, 2026 •

edited

Loading

Uh oh!

netlify Bot commented May 14, 2026 •

edited

Loading

Uh oh!

netlify Bot commented May 14, 2026 •

edited

Loading

Uh oh!

nx-cloud Bot commented May 14, 2026 •

edited

Loading

Uh oh!

This comment was marked as outdated.

Uh oh!

socket-security Bot commented May 15, 2026 •

edited

Loading

Uh oh!

nx-cloud Bot left a comment •

edited

Loading

Uh oh!

socket-security Bot commented Jun 11, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

FrozenPandaz commented May 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

v2 breaking changes and how each is handled

1. @rspack/core@2 is pure ESM at the entry, but the bundle is CJS

2. @rspack/dev-server@2 is a ground-up rewrite — no longer wraps webpack-dev-server

3. Tightened RuleSetRule typings broke flattened oneOf shapes

4. experiments.outputModule no longer accepted in the same shape

5. stats.profile / statsJson no longer accept the v1 shape

6. afterDone may fire with undefined stats on error

7. --watch flag rename in @rsbuild/core@2

8. Peer-dep auto-install picks first satisfiable sub-range

9. Migrations + v1→v2 packageJsonUpdates

10. Docs

Known limitation: rspack serve under Cypress 15

Test Plan

Uh oh!

netlify Bot commented May 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for nx-dev ready!

Uh oh!

netlify Bot commented May 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for nx-docs ready!

Uh oh!

nx-cloud Bot commented May 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

This comment was marked as outdated.

Uh oh!

socket-security Bot commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nx-cloud Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Nx Cloud is proposing a fix for your failed CI:

Uh oh!

socket-security Bot commented Jun 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

FrozenPandaz commented May 14, 2026 •

edited

Loading

1. `@rspack/core@2` is pure ESM at the entry, but the bundle is CJS

2. `@rspack/dev-server@2` is a ground-up rewrite — no longer wraps `webpack-dev-server`

3. Tightened `RuleSetRule` typings broke flattened `oneOf` shapes

4. `experiments.outputModule` no longer accepted in the same shape

5. `stats.profile` / `statsJson` no longer accept the v1 shape

6. `afterDone` may fire with `undefined` stats on error

7. `--watch` flag rename in `@rsbuild/core@2`

9. Migrations + v1→v2 `packageJsonUpdates`

Known limitation: `rspack serve` under Cypress 15

netlify Bot commented May 14, 2026 •

edited

Loading

netlify Bot commented May 14, 2026 •

edited

Loading

nx-cloud Bot commented May 14, 2026 •

edited

Loading

socket-security Bot commented May 15, 2026 •

edited

Loading

nx-cloud Bot left a comment •

edited

Loading

socket-security Bot commented Jun 11, 2026 •

edited

Loading