ArkEnv now runs on Nub

[yamcodes]

ArkEnv is a TypeScript library for typesafe environment variables. You keep ArkType, Zod, Valibot, or any Standard Schema, and you get a typed env object that fails at startup when a value is missing or wrong.

The monorepo now uses Nub for the work that used to be split across pnpm, tsx, dotenv, and nvm. Repo: yamcodes/arkenv (v1).

Package manager. Root packageManager is nub@0.9.3, the lockfile is nub.lock, and nub.jsonc uses an isolated linker. A preinstall script exits if someone runs pnpm, npm, or yarn install in that tree. Node is pinned to 24.21.0 in .node-version; the next nub command provisions that version.

Scripts and TypeScript. Day-to-day commands are nub install, nub run www, nub run test, and nub run changeset. The examples start with nub src/index.ts and nub watch. Nub loads .env* and runs the TypeScript entry. ArkEnv does not load dotenv files itself.

CI. Workflows go through a composite action that calls nubjs/setup-nub@v0 (shim on, Node from .node-version) and then nub install. That covers tests, release, and the docs deploy.

If a project already runs under Nub. Nub loads the env files. ArkEnv validates on import { env } from "./env". To fail before application code runs, point preload at the schema:

{
  "preload": ["./env.ts"]
}

nubx arkenv check runs the same check without starting the app, and it inherits Nub's .env* loading. Guide: Use with Nub.

Nub stays optional for people using ArkEnv. Getting started still shows npx and node --env-file. There is no nub-arkenv plugin and no Varlock-style hand-off: nubx arkenv already runs the CLI, and validation stays on the imported env object. Write-up: ADR 0035.

One sharp edge on deploy: Corepack does not know nub, and the Vercel CLI does not treat nub.lock as a lockfile. CI runs nub install first, then a small wrapper sets VERCEL_INSTALL_COMPLETED=1 so vercel build does not try corepack enable nub or fall back to npm install.