Version Packages#971
Open
arkenv-bot[bot] wants to merge 1 commit into
Open
Conversation
arkenv
@arkenv/bun-plugin
@arkenv/cli
@arkenv/fumadocs-ui
@arkenv/vite-plugin
commit: |
Contributor
Author
📦 Bundle Size Report
✅ All size limits passed! |
Contributor
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
52f7a5f to
b2ec277
Compare
b2ec277 to
7bb3f1f
Compare
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
@arkenv/cli@0.0.6
Patch Changes
Generate
env.d.tsfile for plugins#96993389bd@yamcodesWhen installing the Vite plugin or the Bun plugin, a matching
env.d.tswill be generated if one is not present.If one is present, the CLI will offer to append the necessary types to it.
This allows for typesafety when calling via
process.envorimport.meta.env, see: https://arkenv.js.org/docs/vite-plugin/typing-import-meta-envAdd default values to the initial env keys
07eed0f@yamcodesThe initial env keys (
NODE_ENV,PORT) now recieve default values so the code runs even if the user didn't set them up in their.envfile.