feat: using oxc resolver #39
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
underfin
force-pushed
the
oxc-resolver
branch
from
c8be833
to
b0a6ad4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Alias
matched alias key
The
@rollup/alias-pluginalias key support regex, but the oxc resolver not support it.matched alias value behavior
The vite resolver alias has a case like this { '/@vite/env': '/@fs/xxx' }, It resolved by
@rollup/alias-pluginto/@fs/xxx, and it internal will callPluginContext#resolveIdto resolve/@fs/xxx, it will resolved toxxxby viter-resolver.The oxc resolver alias will matched to
/@fs/xxxand find it not found.Look like the rolldown
BuiltinAliasPlugincould suitable for it.