fix(deps): update dependency arkenv to v0.12.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
arkenv (source)	0.9.2 → 0.12.3

---

Release Notes

yamcodes/arkenv (arkenv)

v0.12.3

Compare Source

Patch Changes

• Improve npm keywords across published packages for discoverability #1383 bf60ab2 @​yamcodes

  Clean up and extend the keywords field of every published package so npm search, aggregators, and LLM-powered package discovery surface ArkEnv for the terms users actually search for.

  • Remove the misleading pnpm keyword from arkenv and add env, environment-variables, dotenv, config, standard-schema, and the supported validators zod and valibot.
  • Deduplicate the repeated arkenv keyword in @arkenv/vite-plugin.
  • Give every env-related package a shared baseline (env, environment-variables, dotenv, config, validation, typesafe, standard-schema) alongside their integration-specific terms.
  • Add a keyword set to @arkenv/fumadocs-ui, which previously had none.

v0.12.2

Compare Source

Patch Changes

• Expose getSchemaKeys helper #1191 a3e32db @​yamcodes

  Expose getSchemaKeys helper and widen RuntimeEnvironment type to support typed framework runtime configurations.

• Handle pre-parsed primitives gracefully in coercion logic #1206 12ed4f3 @​yamcodes

  Updated the core coercion logic to defensively skip values that are not strings. This ensures ArkEnv won't crash or behave unpredictably when passed configuration objects that have already been parsed into numbers, booleans, or complex objects by other systems (such as Nuxt's runtimeConfig).

• Fix coercion to prevent in-place mutation of environment config objects #1206 12ed4f3 @​yamcodes

  Refactor applyCoercion to perform non-mutating updates on environment configuration data. Clone objects and arrays along the validation path instead of modifying them in-place, preventing runtime crashes on frozen configuration objects (e.g., framework runtime configurations) and avoiding side-effects on reusable config objects.

  Usage:

  import { createEnv } from "arkenv";
  
  const env = createEnv(
    { DATABASE: { port: "number" } },
    { env: { DATABASE: Object.freeze({ port: "3000" }) } } // Frozen object is now safely parsed without crashes!
  );

v0.12.1

Compare Source

Patch Changes

• Add emptyAsUndefined option to treat empty env values as missing #1188 3bfbcb7 @​yamcodes

  Add a new emptyAsUndefined configuration option to both createEnv (ArkType mode) and arkenv/standard (Standard Schema mode). When enabled, environment variables set to empty strings (e.g., PORT= in a .env file) are treated as if they were missing, allowing defaults to apply and preventing unnecessary validation errors for numeric, boolean, or array types.

  Usage:

  import arkenv from "arkenv";
  
  const env = arkenv(
    { PORT: "number = 3000", DEBUG: "boolean = false" },
    { emptyAsUndefined: true }
  );
  
  // Given PORT= and DEBUG= in the environment:
  // env.PORT  → 3000
  // env.DEBUG → false

  import arkenv from "arkenv/standard";
  import { z } from "zod";
  
  const env = arkenv(
    { PORT: z.coerce.number().default(3000) },
    { emptyAsUndefined: true }
  );

  • The default behavior remains unchanged (emptyAsUndefined: false).
  • Keys with empty values are removed from the input record before validation so that ArkType defaults and optional types work correctly.

v0.12.0

Compare Source

Minor Changes

• Add Standard JSON Schema coercion to arkenv/standard #1154 88b0eee @​yamcodes

  Introduce opt-out type coercion for standard mode (arkenv/standard). This coercion only works if the validator is a standard JSON Schema compliant validator (e.g., Zod, Valibot, or custom schemas that implement the StandardJSONSchemaV1 interface). This automatically enables coercion for environment variables without relying on ArkType's runtime footprint.

  If you need to disable coercion, explicitly pass { coerce: false } in your configuration:

  import arkenv from "arkenv/standard";
  import { z } from "zod";
  
  const env = arkenv({ PORT: z.number() }, { coerce: false });

  BREAKING CHANGE: Coercion is now enabled by default in arkenv/standard. This will automatically coerce environment variables to their expected types (e.g., strings containing numbers, booleans, or dates will be converted to their respective types) based on the JSON Schema of your validators. It's unlikely to affect you unless you were relying on validation failing for uncoerced string inputs, or have custom schemas that expect raw strings instead of coerced values.

v0.11.1

Compare Source

Patch Changes

• Add Infer<T> helper to resolve environment variable types #1092 c6c30ab @​yamcodes

  Introduce the Infer<T> type helper, allowing developers to extract the inferred output types of their environment schemas. It supports both declarative schema shapes and compiled schemas (like Zod or ArkType types).

  Usage:

  import { createEnv, type Infer } from "arkenv";
  import { type } from "arktype";
  
  const schema = {
    PORT: type.number,
  };
  
  export type Env = Infer<typeof schema>;

v0.11.0

Compare Source

Minor Changes

• Remove ArkEnvError import from "arkenv" #815 5e8025f @​yamcodes

  The ArkEnvError class is now only available via:

  import { ArkEnvError } from "arkenv/core";

v0.10.0

Compare Source

Minor Changes

• arkenv/standard import #806 f9010d0 @​yamcodes

  arkenv now ships three separate entry points:

  • arkenv (main): ArkType-first. Includes createEnv (aliased to arkenv default import), type, and ArkEnvError. Importing from this entry requires you to have ArkType installed.
  • arkenv/standard: ArkType-free. A standalone createEnv (aliased to arkenv default import) for Standard Schema validators (Zod, Valibot, etc.), not requiring ArkType.
  • arkenv/core: Mode-agnostic primitives - ArkEnvError and ValidationIssue.

Breaking changes

**1. `validator: "standard"` option removed; `arkenv` now statically requires ArkType.**
The `validator` config option has been removed - ArkType is now always required when importing from `arkenv`. For a zero-ArkType bundle, use `arkenv/standard`:

```ts
// ❌ Before
import arkenv from "arkenv";
import { z } from "zod";

const env = arkenv({ PORT: z.coerce.number() }, { validator: "standard" });

// ✅ After
import arkenv from "arkenv/standard";
import { z } from "zod";

const env = arkenv({ PORT: z.coerce.number() });
```

**2. `type` moved from `arkenv/arktype` to `arkenv`.**
The `type` helper is now exported from the main entry. The `arkenv/arktype` sub-path is no longer public:

```ts
// ❌ Before
import { type } from "arkenv/arktype";

// ✅ After
import { type } from "arkenv"; // 'type' is the ArkEnv helper, not a TS type modifier
```

v0.9.3

Compare Source

Patch Changes

• Fix inline schema autocompletion #797 8f1b0dd @​yamcodes

  Fixed a regression where editor autocompletion for ArkType DSL strings (e.g. "string", "number.port") stopped working when using arkenv() with an inline schema object. The createEnv overloads are now narrowed by validator config type, making them mutually exclusive and order-independent.

---

Configuration

📅 Schedule: (in timezone Asia/Almaty)

• Branch creation
  • "on friday"
• 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.