[node-resolve] Replace `resolve` and some rollup-baked `exports` fields handling with a Rust-based resolver

[SukkaW]

• Rollup Plugin Name: @rollup/plugin-node-resolve
• Rollup Plugin Version: 16.0.1

Feature Use Case

Currently, @rollup/plugin-node-resolve relies on resolve, a resolver created and maintained by Browserify, which hasn't been actively maintained and lacks the export map feature.

Rollup builds @rollup/plugin-node-resolve on top of resolve with extra code to handle the browser field and export map.

The resolve plugin is a hot path during the build process, ranging from 10 to thousands or even more. Rustifying the resolver could benefit performance.

Feature Proposal

Maybe Rollup could rustify the resolve part, starting with @rollup/plugin-node-resolve. It is possible to use a Rust-based resolver, like oxc-resolver or rspack-resolver directly. Rollup could also build a rollup-flavored one on top of those crates.

Also, those resolvers already support features (that resolve doesn't have) like export map and the browser field, so @rollup/plugin-node-resolve wouldn't need to re-implement those features again.

After experimenting with @rollup/plugin-node-resolve, we could then decide whether the Rollup core's built-in resolver can benefit from rustify as well.

[lukastaegert]

I am not sure if it definitely needs to be "Rust" to improve performance, but I agree that completely owning the resolver will bring benefits. The greatest benefits I actually see from caching all directory accesses etc. during each build, something that currently is only done in the part handled by the old resolve plugin but not by the new parts.
But sure, it can also be Rust as long as jump between JavaScript and Rust does not become another bottleneck.
Unfortunately, I had little resources to pursue anything here, but I would be open if someone else picked it up.

[SukkaW]

The greatest benefits I actually see from caching all directory accesses etc. during each build

I see benefits from native exports and browser features, which are currently still maintained by rollup (which only adds burdens).

But sure, it can also be Rust as long as jump between JavaScript and Rust does not become another bottleneck.

webpack's enhanced-resolve could be the JavaScript alternative and is battle-tested. Also supports exports and browser by default.

[JounQin]

@lukastaegert Just FYI, resolve has been replaced by https://github.com/unrs/unrs-resolver#readme in Jest 30: https://jestjs.io/blog#performance--memory-improvements

[SukkaW]

@lukastaegert Just FYI, resolve has been replaced by https://github.com/unrs/unrs-resolver#readme in Jest 30: https://jestjs.io/blog#performance--memory-improvements

unrs-resolver doesn't support options of @rollup/plugin-node-resolver, and supporting those options will affect performance. So the Jest case doesn't make any points here.

[JounQin]

Then oxc-resolver and @rspack/resolver are even worse, LOL.