Webpack to rspack migration

[ScriptedAlchemy]

Apply compatibility fixes and dependency cleanup to ensure full feature and test support for the Rspack migration.

This PR addresses three key compatibility risks identified during the Rspack migration review:

1. Expanded missing-module fallback: The Rspack resolver hook's isNotFoundError logic was too narrow, only detecting "NotFound" errors. This has been expanded to include "Can't resolve" and "Cannot resolve" messages, restoring webpack-compatible fallback behavior for runtime not-found modules.
2. Removed forced types: ["node"]: The custom TS loader was implicitly forcing types: ["node"], which could introduce unintended Node typings dependencies. This override has been removed to preserve compatibility with prior ts-loader semantics.
3. Dependency hygiene: Several direct dev dependencies (@swc/core, @swc/wasm, @types/node, undici-types) were introduced during migration but are not required for NCC's core behavior. These have been removed from package.json and yarn.lock has been refreshed.

Validation against the main branch confirmed full parity, with 119 tests passing and only 2 known environment-limited native-module tests failing, matching main's baseline behavior.

---

 

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[changeset-bot]

⚠️ No Changeset found

Latest commit: c0a5514

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR