Conversation
- Downgraded vite version - Removed unused dev dependencies - Updated peerDependencies
- Clarify tested Vite versions
- Allow any vite v2.9.18+ version
- Added FAQ section - Explained Vite config hook usage
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Closed
🦋 Changeset detectedLatest commit: 27a869b The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
github-actions
bot
added
docs
Contributor
WalkthroughUpdates documentation and package metadata to declare Vite support from 2.9.18 through 7.x, adds a changeset entry for a patch release, widens peerDependencies for Vite, adds a Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
- Updated tested versions
commit: |
- Added vite-plugin keyword - Explained Vite-only plugin - Supported Vite 2.9.18 - 7.x
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (3)
packages/vite-plugin/README.md (1)
66-71: Add a “Requirements” section (Vite range, Node note).Per docs guidelines, please document env requirements here too. Suggest:
- Supported Vite: 2.9.18–7.x (align with peerDependencies and root README)
- Note Node version guidance (varies by Vite major; defer to user’s Vite version), and that this plugin is Vite‑only.
packages/vite-plugin/package.json (2)
21-24: Peer range looks good; consider simplifying semver.The disjunction is correct. Optionally, you can express as ">=2.9.18 <8" for readability (same effect).
36-45: Keywords ok; remove duplicate “arkenv”.There’s a duplicate keyword ("arkenv"). Trim it.
Apply:
"keywords": [ "arktype", "arkenv", - "arkenv", "environment", "variables", "vite", "plugin", "vite-plugin" ],
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (3)
packages/arkenv/README.md(1 hunks)packages/vite-plugin/README.md(1 hunks)packages/vite-plugin/package.json(2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/README.md
📄 CodeRabbit inference engine (.github/copilot-instructions.md)
Document environment requirements in README files
Files:
packages/vite-plugin/README.mdpackages/arkenv/README.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: test-build (22)
- GitHub Check: pkg-pr-new
- GitHub Check: test-build (lts/*)
🔇 Additional comments (1)
packages/arkenv/README.md (1)
113-113: LGTM; aligns with plugin’s peer range.Vite “2.9.18 to 7.x” matches the plugin’s peerDependencies. Keep this in sync on future bumps.
- Updated vite dependency - Updated vite-tsconfig-paths
Merged
yamcodes
pushed a commit
that referenced
this pull request
Oct 12, 2025
This PR was opened by the [Changesets release](https://github.com/changesets/action) 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@0.7.3 ### Patch Changes - #### Automatic boolean string conversion _[`#218`](#218) [`e554e2b`](e554e2b) [@yamcodes](https://github.com/yamcodes)_ The `boolean` type now accepts `"true"`/`"false"` strings from environment variables and converts them to actual boolean values. This also works with boolean defaults. Example: ```ts import arkenv from "arkenv"; const env = arkenv({ DEBUG: "boolean", ENABLE_FEATURE: "boolean = true", }); console.log(env.DEBUG); console.log(env.ENABLE_FEATURE); ``` Result: ```sh ❯ DEBUG=true npx tsx index.ts true true ``` ## @arkenv/vite-plugin@0.0.13 ### Patch Changes - #### Support Vite 2.x _[`#212`](#212) [`bfe08f6`](bfe08f6) [@yamcodes](https://github.com/yamcodes)_ Extended the supported Vite versions to include **2.9.18** through **7.x** (inclusive). Also, we've added the `vite-plugin` keyword to the `package.json`, and a section in the `README.md` explaining why this plugin is a Vite only plugin (and not a Rollup plugin). <details><summary>Updated 1 dependency</summary> <small> [`e554e2b`](e554e2b) </small> - `arkenv@0.7.3` </details> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
yamcodes
pushed a commit
that referenced
this pull request
Nov 10, 2025
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [@arkenv/vite-plugin](https://arkenv.js.org) ([source](https://redirect.github.com/yamcodes/arkenv)) | [`^0.0.10` -> `^0.0.14`](https://renovatebot.com/diffs/npm/@arkenv%2fvite-plugin/0.0.10/0.0.14) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>yamcodes/arkenv (@​arkenv/vite-plugin)</summary> ### [`v0.0.14`](https://redirect.github.com/yamcodes/arkenv/releases/tag/%40arkenv/vite-plugin%400.0.14) [Compare Source](https://redirect.github.com/yamcodes/arkenv/compare/@arkenv/vite-plugin@0.0.13...@arkenv/vite-plugin@0.0.14) ##### Patch Changes - #### Support array defaults using `type().default()` syntax *[`#224`](https://redirect.github.com/yamcodes/arkenv/pull/224) [`ecf9b64`](https://redirect.github.com/yamcodes/arkenv/commit/ecf9b64a680d3af5c5786b288fda35608590f7a9) [@​yamcodes](https://redirect.github.com/yamcodes)* Fix to an issue where `type("array[]").default(() => [...])` syntax was not accepted by the plugin due to overly restrictive type constraints. The plugin now accepts any string-keyed record while still maintaining type safety through ArkType's validation system. ##### New Features - Array defaults to empty using `type("string[]").default(() => [])` syntax - Support for complex array types with defaults - Mixed schemas combining string-based and type-based defaults ##### Example ```typescript // vite.config.ts import arkenv from "@​arkenv/vite-plugin"; import { type } from "arkenv"; export default defineConfig({ plugins: [ arkenv({ ALLOWED_ORIGINS: type("string[]").default(() => ["localhost"]), FEATURE_FLAGS: type("string[]").default(() => []), PORT: "number.port", }), ], }); ``` > \[!NOTE] > This is the same fix as in [`arkenv@0.7.2` (the core library)](https://redirect.github.com/yamcodes/arkenv/releases/tag/arkenv%400.7.2), but for the Vite plugin. - #### Fix `import.meta.env` not respecting morphed environment variables *[`#227`](https://redirect.github.com/yamcodes/arkenv/pull/227) [`d41878f`](https://redirect.github.com/yamcodes/arkenv/commit/d41878fe9cc2524f06ac2f0ef35f2f5ba58ee06b) [@​yamcodes](https://redirect.github.com/yamcodes)* The Vite plugin now properly exposes transformed environment variables through `import.meta.env`. Previously, type transformations (`string → number`, `string → boolean`) and default values were lost because the plugin only called `createEnv()` without integrating the results with Vite's environment system. Now the plugin uses Vite's `define` option to expose the morphed values, ensuring all schema transformations are respected. ### [`v0.0.13`](https://redirect.github.com/yamcodes/arkenv/releases/tag/%40arkenv/vite-plugin%400.0.13) [Compare Source](https://redirect.github.com/yamcodes/arkenv/compare/@arkenv/vite-plugin@0.0.12...@arkenv/vite-plugin@0.0.13) ##### Patch Changes - #### Support Vite 2.x *[`#212`](https://redirect.github.com/yamcodes/arkenv/pull/212) [`bfe08f6`](https://redirect.github.com/yamcodes/arkenv/commit/bfe08f6d9f21352186420f0f68611840e164da52) [@​yamcodes](https://redirect.github.com/yamcodes)* Extended the supported Vite versions to include **2.9.18** through **7.x** (inclusive). Also, we've added the `vite-plugin` keyword to the `package.json`, and a section in the `README.md` explaining why this plugin is a Vite only plugin (and not a Rollup plugin). <details><summary>Updated 1 dependency</summary> <small> [`e554e2b`](https://redirect.github.com/yamcodes/arkenv/commit/e554e2b41aab1b8e29d873982ea587c069f4732d) </small> - `arkenv@0.7.3` </details> ### [`v0.0.12`](https://redirect.github.com/yamcodes/arkenv/releases/tag/%40arkenv/vite-plugin%400.0.12) [Compare Source](https://redirect.github.com/yamcodes/arkenv/compare/@arkenv/vite-plugin@0.0.11...@arkenv/vite-plugin@0.0.12) ##### Patch Changes <details><summary>Updated 1 dependency</summary> <small> [`e50dba1`](https://redirect.github.com/yamcodes/arkenv/commit/e50dba1f19418f8fc007dc786df1172067e3d07c) </small> - `arkenv@0.7.2` </details> ### [`v0.0.11`](https://redirect.github.com/yamcodes/arkenv/releases/tag/%40arkenv/vite-plugin%400.0.11) [Compare Source](https://redirect.github.com/yamcodes/arkenv/compare/@arkenv/vite-plugin@0.0.10...@arkenv/vite-plugin@0.0.11) ##### Patch Changes <details><summary>Updated 1 dependency</summary> <small> [`221f9ef`](https://redirect.github.com/yamcodes/arkenv/commit/221f9efdef65691b0c5155b12ec460404dddbe82) [`221f9ef`](https://redirect.github.com/yamcodes/arkenv/commit/221f9efdef65691b0c5155b12ec460404dddbe82) </small> - `arkenv@0.7.1` </details> </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on friday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/yamcodes/arkenv). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNzMuMSIsInVwZGF0ZWRJblZlciI6IjQxLjE3My4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
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
1 participant
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.
Closes #211
Summary by CodeRabbit
Documentation
Chores