arkenv@0.11.0

Minor Changes

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

  The ArkEnvError class is now only available via:

  import { ArkEnvError } from "arkenv/core";

@arkenv/vite-plugin@0.0.32

Patch Changes

Updated 1 dependency

5e8025f

• arkenv@0.11.0

@arkenv/bun-plugin@0.1.6

Patch Changes

Updated 1 dependency

5e8025f

• arkenv@0.11.0

@arkenv/bun-plugin@0.1.5

Patch Changes

• Support NODE_ENV in schema #804 6f8b4f0 @joakimbeng

  When NODE_ENV is included in your schema, it is now validated at startup and correctly typed.

  // src/env.ts
  import { type } from "arkenv";
  
  export default type({
    BUN_PUBLIC_API_URL: "string.url",
    NODE_ENV: "'development' | 'production' | 'test'",
  });

  // process.env.NODE_ENV is now typed as "development" | "production" | "test"
  <p>Mode: {process.env.NODE_ENV}</p>

arkenv@0.10.0

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:

  // ❌ 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:

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

@arkenv/vite-plugin@0.0.31

Patch 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:

  // ❌ 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:

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

Updated 1 dependency

f9010d0

• arkenv@0.10.0

@arkenv/fumadocs-ui@0.0.3

Patch Changes

• Fix misconfigured package.json a23997c @yamcodes

  Fix misconfigured package.json by adding the repository.url field. This fixes an issue with pkg-pr-new and adheres to best practices.

@arkenv/bun-plugin@0.1.4

Patch Changes

Updated 1 dependency

f9010d0

• arkenv@0.10.0

arkenv@0.9.3

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.

@arkenv/vite-plugin@0.0.30

Patch Changes

Updated 1 dependency

8f1b0dd

• arkenv@0.9.3