feat(defineEnv): support resolving paths #373
Merged
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
vicb
reviewed
Dec 12, 2024
vicb
approved these changes
Dec 12, 2024
|
One thing left, we need to add |
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.
This PR adds a feature to new
defineEnvutil (introduced in #372) to allow resolving env config with absolute resolved paths.ESM resolves are made using mlly (using the same Node.js ESM resolution logic with CJS compat and more features)
Resolve paths can be configured to extended. by default, a resolution from
unenvitself will be done as last fallback.Pending #374 to allow external presets paths.(updates tiny change on #374 to usemeta.urlwith ESM compat for URL)