chore: update versions#27
Merged
Merged
Conversation
Releases: @vlandoss/env@0.5.0 [skip ci]
This file contains hidden or 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
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@vlandoss/env@0.5.0
Minor Changes
#26
d355e6fThanks @rqbazan! - TheenvConfig()Vite plugin can now select the env from aVITE_ENVenv var instead of requiring--mode.The plugin reads
VITE_ENVfromprocess.envand your.env*files (via Vite'sloadEnv, so inline/shell values win over file values) and uses it to pick the per-env#configfile and the__ENV_NAME__build constant. WhenVITE_ENVis unset or empty it falls back to Vite'smode, sovite build --mode stagingkeeps working unchanged — this is purely additive.# These are now equivalent: VITE_ENV=staging vite build vite build --mode stagingThe var name is configurable with the new
envVaroption (default"VITE_ENV"):