Skip to content

chore: update versions#27

Merged
rqbazan merged 1 commit into
mainfrom
changeset-release/main
Jun 16, 2026
Merged

chore: update versions#27
rqbazan merged 1 commit into
mainfrom
changeset-release/main

Conversation

@vland-bot

@vland-bot vland-bot Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

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 d355e6f Thanks @rqbazan! - The envConfig() Vite plugin can now select the env from a VITE_ENV env var instead of requiring --mode.

    The plugin reads VITE_ENV from process.env and your .env* files (via Vite's loadEnv, so inline/shell values win over file values) and uses it to pick the per-env #config file and the __ENV_NAME__ build constant. When VITE_ENV is unset or empty it falls back to Vite's mode, so vite build --mode staging keeps working unchanged — this is purely additive.

    # These are now equivalent:
    VITE_ENV=staging vite build
    vite build --mode staging

    The var name is configurable with the new envVar option (default "VITE_ENV"):

    envConfig({ envVar: "APP_ENV" });

Releases:
  @vlandoss/env@0.5.0

[skip ci]
@rqbazan rqbazan merged commit ecf9104 into main Jun 16, 2026
@rqbazan rqbazan deleted the changeset-release/main branch June 16, 2026 00:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant