chore(deps): update rspack and babel dependencies to latest versions

[UnschooledGamer]

Check list

• Test Terminal installation
• Build test on Linux

[greptile-apps]

Greptile Summary

This PR upgrades rspack from v1 to v2 (^1.7.0 → ^2.0.0) along with companion bumps to all Babel, CodeMirror, and various runtime packages, and applies the required v2 migration adjustments in rspack.config.js.

• rspack v2 migration in rspack.config.js: adds module.parser.javascript options (exportsPresence: 'auto', requireAlias: false), sets resolve.roots: [] explicitly to match the new v2 default, and moves type: 'javascript/auto' before the use array (cosmetic reorder).
• Babel direct dependencies: @babel/generator, @babel/parser, and @babel/traverse are now listed as explicit devDependencies, correctly reflecting their direct use in utils/custom-loaders/html-tag-jsx-loader.js.
• Removed entry: com.foxdebug.acode.rk.exec.proot is dropped from devDependencies, unrelated to the dep bump but bundled in the same commit.

Confidence Score: 4/5

Dependency updates are well-scoped and the rspack v2 migration shims are structurally correct; the two config choices worth double-checking are exportsPresence and the empty roots array.

The upgrade applies the documented rspack v2 migration steps correctly. The exportsPresence: auto setting softens the stricter v2 default, which could let real missing-export bugs pass as warnings rather than build errors. The resolve.roots: [] change is the correct v2 default but will silently break any SCSS/CSS files that reference assets with server-relative paths.

rspack.config.js — the new parser and resolve options warrant a quick review against the actual build output and stylesheet asset paths.

Important Files Changed

Filename	Overview
package.json	Version bumps for rspack (^1.7.0 to ^2.0.0), all major Babel packages, and several runtime dependencies; adds @babel/generator, @babel/parser, @babel/traverse as explicit devDependencies (previously implicit transitive deps); removes the proot plugin entry.
rspack.config.js	Adds rspack v2 migration shims: moves type javascript/auto before use array (cosmetic), adds module.parser.javascript options (exportsPresence auto, requireAlias false), and sets resolve.roots to empty array explicitly to match the new v2 default.
package-lock.json	Lock-file updated to reflect all version bumps in package.json; no structural anomalies.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[rspack v2 build start] --> B{module.parser.javascript}
    B --> C["exportsPresence: auto"]
    C --> D{Is module strict ESM?}
    D -->|Yes| E[Error on missing export]
    D -->|No - CJS| F[Warning only - may be silent]
    B --> G["requireAlias: false"]
    G --> H["require calls bypass resolve.alias"]
    A --> I{resolve config}
    I --> J["roots: empty array"]
    J --> K["Server-relative CSS paths no longer resolve to project root"]
    A --> M[CSS/SCSS rule]
    M --> N["type: javascript/auto before use array"]
    N --> O[CssExtractRspackPlugin loader chain]

Loading

_{Reviews (1): Last reviewed commit: "chore: update dependencies" | Re-trigger Greptile}

[greptile-apps]

resolve.roots: [] disables server-relative path resolution

In rspack v1, resolve.roots defaulted to [context] so CSS url(/some/image.png) references resolved relative to the project root. Setting it to [] (the v2 default) removes that implicit root, meaning any existing SCSS/CSS that uses server-relative paths starting with / will now fail to resolve at build time. This is the correct v2 migration step, but if the project's stylesheets contain such paths they should be converted to relative paths (or roots should be restored to [context]) before landing this change.

[UnschooledGamer]

Its seemingly working fine as-is. It should just default to http://localhost/fonts/font.tff etc, if no roots have been given I think

[UnschooledGamer]

@greptile Its seemingly working fine as-is. It should just default to http://localhost/fonts/font.tff etc, if no roots have been given I think

[greptile-apps]

That's a fair point. When roots is empty, rspack won't attempt to resolve server-relative paths (/fonts/font.ttf) against the filesystem at build time — it leaves them as-is, and the browser resolves them against the origin at runtime (http://localhost/fonts/font.ttf). So there's no build failure, just a shift from static to runtime resolution.

If the project's assets are served correctly at those paths (which your testing confirms they are), this is working as intended. My concern was a build-time error scenario that doesn't apply here.

Tip: You can give me more context with [.greptile/rules.md](https://www.greptile.com/docs/code-review/custom-standards) so I get this right next time.