You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Fix import.meta.env not respecting morphed environment variables #227d41878f@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.
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).
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
github-actionsbot
added
the
example
Issues or Pull Requests concerning at least one ArkEnv example. (Found in the `examples/` directory)
label
Nov 10, 2025
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
exampleIssues or Pull Requests concerning at least one ArkEnv example. (Found in the `examples/` directory)
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.
This PR contains the following updates:
^0.0.10->^0.0.14Release Notes
yamcodes/arkenv (@arkenv/vite-plugin)
v0.0.14Compare Source
Patch Changes
Support array defaults using
type().default()syntax#224ecf9b64@yamcodesFix 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
type("string[]").default(() => [])syntaxExample
Fix
import.meta.envnot respecting morphed environment variables#227d41878f@yamcodesThe 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 calledcreateEnv()without integrating the results with Vite's environment system.Now the plugin uses Vite's
defineoption to expose the morphed values, ensuring all schema transformations are respected.v0.0.13Compare Source
Patch Changes
Support Vite 2.x
#212bfe08f6@yamcodesExtended the supported Vite versions to include 2.9.18 through 7.x (inclusive).
Also, we've added the
vite-pluginkeyword to thepackage.json, and a section in theREADME.mdexplaining why this plugin is a Vite only plugin (and not a Rollup plugin).Updated 1 dependency
e554e2barkenv@0.7.3v0.0.12Compare Source
Patch Changes
Updated 1 dependency
e50dba1arkenv@0.7.2v0.0.11Compare Source
Patch Changes
Updated 1 dependency
221f9ef221f9efarkenv@0.7.1Configuration
📅 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.
This PR was generated by Mend Renovate. View the repository job log.