fix: sort aliases to ensure priority is given to more specific aliases #388
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.
π Linked issue
resolves #378, see also unjs/unenv#45
β Type of change
π Description
A couple of issues have come up recently about alias ordering. This PR applies a fix to order aliases by specificity (e.g. number of slashes) meaning we should always have more specific alias in front of general (
fs/promises
in front offs
).The upstream PR to unenv resolves it more specifically within the unenv presets but this is still worth merging here as there are other potential aliases involved.
π Checklist