Skip to content

Releases: yamcodes/arkenv

@arkenv/vite-plugin@0.0.33

03 Apr 15:25
a2365b6

Choose a tag to compare

@arkenv/fumadocs-ui@0.0.7

03 Apr 15:25
a2365b6

Choose a tag to compare

Patch Changes

@arkenv/fumadocs-ui@0.0.6

06 Mar 19:20
ca7fa3e

Choose a tag to compare

Patch Changes

@arkenv/fumadocs-ui@0.0.5

06 Mar 18:41
1009ed3

Choose a tag to compare

Patch Changes

@arkenv/fumadocs-ui@0.0.4

06 Mar 17:41
9468ae0

Choose a tag to compare

Patch Changes

  • Add Header component #828 e1f3183 @yamcodes

    @arkenv/fumadocs-ui now exports a Header component for building site-wide navigation headers.

    import { Header } from "@arkenv/fumadocs-ui/components";
    
    <Header
      logo={<MyLogo />}
      links={[
        { text: "Docs", url: "/docs" },
        { text: "Blog", url: "/blog" },
      ]}
      actions={[<SearchToggle />, <ThemeToggle />]}
      menuActions={[<ThemeToggle />]}
      menuSocialActions={[<GitHubLink />]}
      sidebarTrigger={<MySidebarTrigger />}
    />;

    The header is fixed to the top of the viewport and adapts its appearance as the user scrolls — transparent when at the top of the page, blurred with a semi-transparent background once the user scrolls down.

    On mobile the header renders a full-screen dropdown menu. Nav links are stacked at the top, an "Appearance" row (label + menuActions) sits above a centered row of menuSocialActions. An optional sidebarTrigger slot renders left of the logo for layouts that have a docs sidebar.

  • Expand css/theme.css #828 e1f3183 @yamcodes

    @arkenv/fumadocs-ui/css/theme.css now includes a complete set of fumadocs override styles so any app importing the theme gets correct defaults out of the box: nav/header height variables, sidebar drawer positioning (left-side on mobile), z-index stack (header → backdrop → sidebar drawer → search dialog → Radix poppers), search bar colors, external link icons, link underline styles, and heading anchor alignment.

arkenv@0.11.0

24 Feb 20:25
3fd1534

Choose a tag to compare

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

24 Feb 20:25
3fd1534

Choose a tag to compare

Patch Changes

Updated 1 dependency

5e8025f

  • arkenv@0.11.0

@arkenv/bun-plugin@0.1.6

24 Feb 20:25
3fd1534

Choose a tag to compare

Patch Changes

Updated 1 dependency

5e8025f

  • arkenv@0.11.0

@arkenv/bun-plugin@0.1.5

23 Feb 18:21
41b2908

Choose a tag to compare

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

22 Feb 19:59
65e3bbf

Choose a tag to compare

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