Version Packages

[arkenv-bot]

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@0.8.0

Minor Changes

• Coercion #569 adaada4 @yamcodes

  Introduced Schema-Directed Coercion: now, environment variables defined as number or boolean in your schema are automatically parsed to their correct types.

  If you want to opt-out of this feature, pass config.coerce: false to createEnv() (arkenv()). Example:

  arkenv(schema, { coerce: false });

  To learn more about the new coercion system, read the docs.

  • BREAKING: The createEnv() function signature has changed to support a configuration object.
    Instead of createEnv(schema, env), use createEnv(schema, config) where config includes env (process.env by default, like before) and the newly added coerce option (true by default).
    For example, Vite users might need to update their vite.config.ts:

    const env = arkenv(Env, { env: loadEnv(mode, process.cwd(), "") });

  • BREAKING: The custom boolean morph has been removed. We now use arktype's standard boolean instead, which is coerced when used within createEnv / arkenv. This is only breaking if you specifically use boolean unrelated to createEnv / arkenv / our plugins and expect it to be coerced.
  • BREAKING: number.port is now a strict numeric refinement (0-65535). It no longer parses strings automatically outside of createEnv / arkenv. This is only breaking if you specifically use port unrelated to createEnv / arkenv / our plugins and expect it to be parsed as a number.

Patch Changes

• Fix error formatting #582 674a2ad @aruaycodes

  The ArkEnv error message is now formatted better, using correct spacing and removing the f prefix.

  Before:

  apps/playgrounds/node on  main [$] via 🤖 v24.11.1
  ❯ ns
  
  > node-playground@ start /Users/yamcodes/code/arkenv/apps/playgrounds/node
  > tsx --env-file .env index.ts
  
  /Users/yamcodes/code/arkenv/packages/arkenv/src/create-env.ts:49
                  throw new ArkEnvError(validatedEnv);
                        ^
  
  f [ArkEnvError]: Errors found while validating environment variables
    ZED_ENV must be present (was missing)
  
      at m (/Users/yamcodes/code/arkenv/packages/arkenv/src/create-env.ts:49:9)
      at <anonymous> (/Users/yamcodes/code/arkenv/apps/playgrounds/node/index.ts:4:13)
      at ModuleJob.run (node:internal/modules/esm/module_job:377:25)
      at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:671:26)
      at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:101:5)
  
  Node.js v24.11.1
   ELIFECYCLE  Command failed with exit code 1.
  

  After:

  apps/playgrounds/node on  improve-error-formatting [$?] via 🤖 v24.11.1
  ❯ ns
  
  > node-playground@ start /Users/yamcodes/code/arkenv/apps/playgrounds/node
  > tsx --env-file .env index.ts
  
  /Users/yamcodes/code/arkenv/packages/arkenv/src/create-env.ts:49
                  throw new ArkEnvError(validatedEnv);
                        ^
  
  ArkEnvError: Errors found while validating environment variables
    ZED_ENV must be present (was missing)
  
      at m (/Users/yamcodes/code/arkenv/packages/arkenv/src/create-env.ts:49:9)
      at <anonymous> (/Users/yamcodes/code/arkenv/apps/playgrounds/node/index.ts:4:13)
      at ModuleJob.run (node:internal/modules/esm/module_job:377:25)
      at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:671:26)
      at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:101:5)
  
  Node.js v24.11.1
   ELIFECYCLE  Command failed with exit code 1.
  

@arkenv/bun-plugin@0.0.5

Patch Changes

Updated 1 dependency

adaada4 674a2ad

• arkenv@0.8.0

@arkenv/vite-plugin@0.0.22

Patch Changes

Updated 1 dependency

adaada4 674a2ad

• arkenv@0.8.0

@repo/keywords@0.1.0

Minor Changes

• Simplify keywords for central coercion #569 adaada4 @yamcodes

  • BREAKING: The boolean keyword has been removed. Universal boolean coercion is now handled by the arkenv package.
  • BREAKING: The port keyword has been changed from a string -> number morph to a pure number refinement. Numeric coercion is now handled centrally.
  • Added maybeParsedNumber and maybeParsedBoolean internal morphs to support central coercion (including specific "NaN" support).

@repo/scope@0.1.0

Minor Changes

• Align scope with central coercion #569 adaada4 @yamcodes

  • BREAKING: Removed the custom boolean keyword from the root scope. ArkEnv now uses the standard ArkType boolean primitive combined with global coercion.
  • Updated number.port to use the new strict numeric refinement, as string parsing is now handled by global coercion.

Patch Changes

Updated 1 dependency

adaada4

• @repo/keywords@0.1.0

@repo/types@1.0.0

Patch Changes

Updated 1 dependency

adaada4

• @repo/scope@0.1.0

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
arkenv	Ready	Preview, Comment	Dec 22, 2025 6:25pm

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/arkenv@585

npm i https://pkg.pr.new/@arkenv/bun-plugin@585

npm i https://pkg.pr.new/@arkenv/vite-plugin@585

commit: a4a5c79

[arkenv-bot]

📦 Bundle Size Report

Package	Size	Limit	Diff	Status
arkenv	1.41 kB	2 kB	+98.3%	✅
@arkenv/bun-plugin	2.06 kB	2.2 kB	+47.9%	✅
@arkenv/vite-plugin	1.54 kB	2 kB	+77.8%	✅

✅ All size limits passed!

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 13 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/yamcodes?upgradeToPro=build-rate-limit

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 5 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/yamcodes?upgradeToPro=build-rate-limit

[yamcodes]

Damn it, Vercel is rate limiting us, because of the constant preview deployments which now blocked our production deployment :/

I opened #605 to discuss some solutions