Releases: yamcodes/arkenv
@arkenv/vite-plugin@0.0.33
@arkenv/fumadocs-ui@0.0.7
@arkenv/fumadocs-ui@0.0.6
@arkenv/fumadocs-ui@0.0.5
@arkenv/fumadocs-ui@0.0.4
Patch Changes
-
Add
Headercomponent#828e1f3183@yamcodes@arkenv/fumadocs-uinow exports aHeadercomponent 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 ofmenuSocialActions. An optionalsidebarTriggerslot renders left of the logo for layouts that have a docs sidebar. -
Expand
css/theme.css#828e1f3183@yamcodes@arkenv/fumadocs-ui/css/theme.cssnow 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
@arkenv/vite-plugin@0.0.32
Patch Changes
@arkenv/bun-plugin@0.1.6
Patch Changes
@arkenv/bun-plugin@0.1.5
Patch Changes
-
Support
NODE_ENVin schema#8046f8b4f0@joakimbengWhen
NODE_ENVis 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/standardimport#806f9010d0@yamcodesarkenvnow ships three separate entry points:arkenv(main): ArkType-first. IncludescreateEnv(aliased toarkenvdefault import),type, andArkEnvError. Importing from this entry requires you to have ArkType installed.arkenv/standard: ArkType-free. A standalonecreateEnv(aliased toarkenvdefault import) for Standard Schema validators (Zod, Valibot, etc.), not requiring ArkType.arkenv/core: Mode-agnostic primitives -ArkEnvErrorandValidationIssue.
Breaking changes
1.
validator: "standard"option removed;arkenvnow statically requires ArkType.
Thevalidatorconfig option has been removed - ArkType is now always required when importing fromarkenv. For a zero-ArkType bundle, usearkenv/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.
typemoved fromarkenv/arktypetoarkenv.
Thetypehelper is now exported from the main entry. Thearkenv/arktypesub-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