Version Packages (rc)

[arkenv-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to v1, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

v1 is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on v1.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@arkenv/build@1.0.0-rc.3

Major Changes

• Remove the SharedSchema key extractors #2011 9483c3c @yamcodes

  extractSharedKeys and extractSharedBlock are no longer exported from @arkenv/build. @arkenv/nextjs/config and @arkenv/nuxt (including @arkenv/nuxt/standard/config) no longer re-export extractSharedKeys. Shared keys in a flat arkenv() call still come from extractKeys and classifyEnvKeys.

  BREAKING CHANGE: Those helpers scanned source for a SharedSchema = { ... } assignment. Classify a flat arkenv() call instead.

   import { classifyEnvKeys } from "@arkenv/build";
   
   const { sharedKeys } = classifyEnvKeys(source, ["NEXT_PUBLIC_"]);

Patch Changes

• Reject runtime keys in the plugin option guard #2012 87f3743 @yamcodes

  The shared transform-option guard now treats env, coerce, onUndeclaredKey, arrayFormat, emptyAsUndefined, debugSecrets, and toJsonSchema as unsupported plugin options. The build reads the loaded environment.

@arkenv/bun-plugin@1.0.0-rc.3

Major Changes

• Export only arkenvPlugin from the Bun plugin #2015 7417dd7 @yamcodes

  @arkenv/bun-plugin and @arkenv/bun-plugin/standard now export arkenvPlugin as the default and the only named export. The arkenvBunPlugin and hybrid aliases have been removed. arkenvPlugin is still both a factory and a plugin object with name, target, and setup.

   import arkenvPlugin from "@arkenv/bun-plugin";
   
   await Bun.build({
     plugins: [arkenvPlugin],
   });

  BREAKING CHANGE: arkenvBunPlugin and hybrid are no longer exported. Use arkenvPlugin instead.

• Reject runtime options on bundler plugins #2012 87f3743 @yamcodes

  Vite, Bun, and Rsbuild plugins now accept only schemaPath, clientPrefix, logger, and logLevel. The build validates the environment loaded for that compile. Variables already set on process.env win over env files.

   import { arkenvPlugin } from "@arkenv/vite-plugin";
   
   export default {
     plugins: [arkenvPlugin({ schemaPath: "src/env.ts" })],
   };

  Set env, coerce, onUndeclaredKey, arrayFormat, emptyAsUndefined, debugSecrets, and toJsonSchema on arkenv() in env.ts. The plugin rejects those keys.

   import arkenv from "@arkenv/core";
   
   export const env = arkenv(
     { PORT: "number" },
     { coerce: true, onUndeclaredKey: "reject" },
   );

  BREAKING CHANGE: Plugin option types no longer include runtime arkenv() fields, including env. Passing them now throws.

   - arkenvPlugin({ env: { PORT: "3000" }, coerce: true })
   + arkenvPlugin({ schemaPath: "src/env.ts" })

Patch Changes

Updated 3 dependencies

87f3743 9483c3c 089ef43

• @arkenv/build@1.0.0-rc.3
• @arkenv/core@1.0.0-rc.3
• @arkenv/standard@1.0.0-rc.3

## @arkenv/nextjs@1.0.0-rc.3

Major Changes

• Remove the SharedSchema key extractors #2011 9483c3c @yamcodes

  extractSharedKeys and extractSharedBlock are no longer exported from @arkenv/build. @arkenv/nextjs/config and @arkenv/nuxt (including @arkenv/nuxt/standard/config) no longer re-export extractSharedKeys. Shared keys in a flat arkenv() call still come from extractKeys and classifyEnvKeys.

  BREAKING CHANGE: Those helpers scanned source for a SharedSchema = { ... } assignment. Classify a flat arkenv() call instead.

   import { classifyEnvKeys } from "@arkenv/build";
   
   const { sharedKeys } = classifyEnvKeys(source, ["NEXT_PUBLIC_"]);

Patch Changes

Updated 3 dependencies

87f3743 9483c3c 089ef43

• @arkenv/build@1.0.0-rc.3
• @arkenv/core@1.0.0-rc.3
• @arkenv/standard@1.0.0-rc.3

## @arkenv/nuxt@1.0.0-rc.3

Major Changes

• Remove the SharedSchema key extractors #2011 9483c3c @yamcodes

  extractSharedKeys and extractSharedBlock are no longer exported from @arkenv/build. @arkenv/nextjs/config and @arkenv/nuxt (including @arkenv/nuxt/standard/config) no longer re-export extractSharedKeys. Shared keys in a flat arkenv() call still come from extractKeys and classifyEnvKeys.

  BREAKING CHANGE: Those helpers scanned source for a SharedSchema = { ... } assignment. Classify a flat arkenv() call instead.

   import { classifyEnvKeys } from "@arkenv/build";
   
   const { sharedKeys } = classifyEnvKeys(source, ["NEXT_PUBLIC_"]);

Patch Changes

Updated 3 dependencies

87f3743 9483c3c 089ef43

• @arkenv/build@1.0.0-rc.3
• @arkenv/core@1.0.0-rc.3
• @arkenv/standard@1.0.0-rc.3

## @arkenv/rsbuild-plugin@1.0.0-rc.3

Major Changes

• Export only arkenvPlugin from the Rsbuild plugin #2015 7417dd7 @yamcodes

  @arkenv/rsbuild-plugin and @arkenv/rsbuild-plugin/standard now export arkenvPlugin as the default and the only named export. The arkenvRsbuildPlugin alias has been removed.

   import { arkenvPlugin } from "@arkenv/rsbuild-plugin";
   
   export default defineConfig({
     plugins: [arkenvPlugin()],
   });

  BREAKING CHANGE: arkenvRsbuildPlugin is no longer exported. Import arkenvPlugin instead.

• Reject runtime options on bundler plugins #2012 87f3743 @yamcodes

  Vite, Bun, and Rsbuild plugins now accept only schemaPath, clientPrefix, logger, and logLevel. The build validates the environment loaded for that compile. Variables already set on process.env win over env files.

   import { arkenvPlugin } from "@arkenv/vite-plugin";
   
   export default {
     plugins: [arkenvPlugin({ schemaPath: "src/env.ts" })],
   };

  Set env, coerce, onUndeclaredKey, arrayFormat, emptyAsUndefined, debugSecrets, and toJsonSchema on arkenv() in env.ts. The plugin rejects those keys.

   import arkenv from "@arkenv/core";
   
   export const env = arkenv(
     { PORT: "number" },
     { coerce: true, onUndeclaredKey: "reject" },
   );

  BREAKING CHANGE: Plugin option types no longer include runtime arkenv() fields, including env. Passing them now throws.

   - arkenvPlugin({ env: { PORT: "3000" }, coerce: true })
   + arkenvPlugin({ schemaPath: "src/env.ts" })

Patch Changes

Updated 3 dependencies

87f3743 9483c3c 089ef43

• @arkenv/build@1.0.0-rc.3
• @arkenv/core@1.0.0-rc.3
• @arkenv/standard@1.0.0-rc.3

## @arkenv/vite-plugin@1.0.0-rc.3

Major Changes

• Export only arkenvPlugin from the Vite plugin #2015 7417dd7 @yamcodes

  @arkenv/vite-plugin and @arkenv/vite-plugin/standard now export arkenvPlugin as the default and the only named export. The arkenvVitePlugin alias has been removed.

   import arkenvPlugin from "@arkenv/vite-plugin";
   
   export default defineConfig({
     plugins: [arkenvPlugin()],
   });

  BREAKING CHANGE: arkenvVitePlugin is no longer exported. Import arkenvPlugin instead.

• Reject runtime options on bundler plugins #2012 87f3743 @yamcodes

  Vite, Bun, and Rsbuild plugins now accept only schemaPath, clientPrefix, logger, and logLevel. The build validates the environment loaded for that compile. Variables already set on process.env win over env files.

   import { arkenvPlugin } from "@arkenv/vite-plugin";
   
   export default {
     plugins: [arkenvPlugin({ schemaPath: "src/env.ts" })],
   };

  Set env, coerce, onUndeclaredKey, arrayFormat, emptyAsUndefined, debugSecrets, and toJsonSchema on arkenv() in env.ts. The plugin rejects those keys.

   import arkenv from "@arkenv/core";
   
   export const env = arkenv(
     { PORT: "number" },
     { coerce: true, onUndeclaredKey: "reject" },
   );

  BREAKING CHANGE: Plugin option types no longer include runtime arkenv() fields, including env. Passing them now throws.

   - arkenvPlugin({ env: { PORT: "3000" }, coerce: true })
   + arkenvPlugin({ schemaPath: "src/env.ts" })

Patch Changes

Updated 3 dependencies

87f3743 9483c3c 089ef43

• @arkenv/build@1.0.0-rc.3
• @arkenv/core@1.0.0-rc.3
• @arkenv/standard@1.0.0-rc.3

## arkenv@1.0.0-rc.3

Minor Changes

• Stop installing the agent skill during init #1984 2c1dd0f @yamcodes

  arkenv init no longer prompts for or installs the ArkEnv agent skill, including under --yes. When the skill is not already in the project, the next-steps note still prints npx skills add yamcodes/arkenv. @arkenv/agent-plugin already includes the skill.

• Scaffold arkenvPlugin in Vite and Rsbuild configs #2015 7417dd7 @yamcodes

  arkenv init now writes arkenvPlugin into new Vite and Rsbuild config entries. Vite binds the default import as arkenvPlugin. Rsbuild imports the named arkenvPlugin.

   import arkenvPlugin from "@arkenv/vite-plugin";
   
   export default defineConfig({
     plugins: [arkenvPlugin()],
   });

Patch Changes

• Scaffold Zod and Valibot init on standard mode #2020 a3815e6 @yamcodes

  arkenv init no longer installs arktype when you choose Zod or Valibot. Next.js, Nuxt, Vite, Rsbuild, and Bun now scaffold the /standard integration entry, and Next.js and Nuxt also install @arkenv/standard.

   import arkenv from "@arkenv/nuxt/standard";
   import * as z from "zod";
   
   export const env = arkenv({
     DATABASE_URL: z.url(),
   });

  Re-running init replaces the other engine's entry. A Nuxt app that still registers @arkenv/nuxt/module switches to @arkenv/nuxt/standard/module when you choose Zod or Valibot, and the same replacement applies to the Next.js, Vite, and Rsbuild imports. Choosing ArkType switches those entries back.

  ArkType init is unchanged: it still installs arktype and uses the ArkType integration entry.

@arkenv/agent-plugin@1.0.0-rc.2

Patch Changes

• Parse audit sources with the TypeScript 7 sync API #1990 f3039bf @yamcodes

  The agent plugin audit now parses source files through typescript/unstable/sync instead of the classic TypeScript compiler API.

• Point init refusals at nextActions #1977 dd2fa82 @yamcodes

  Agent instructions now tell you to retry only when a refusal's nextActions include a run-command with --force.

@arkenv/core@1.0.0-rc.3

Patch Changes

• Restore keyword suggestions inside inline schemas #1975 089ef43 @yamcodes

  A partial keyword in an inline schema string suggests ArkType keywords again. arkenv({ PORT: "n" }) offers never, null, and number. The same suggestions are back on arkenv from @arkenv/core/safe.

   import arkenv from "@arkenv/core";
   
   export const env = arkenv({
     PORT: "number.port = 3000",
   });

@arkenv/tanstack-addon@1.0.0-rc.2

Patch Changes

• Scaffold arkenvPlugin in the TanStack add-on #2015 7417dd7 @yamcodes

  The TanStack CLI add-on now registers the Vite plugin as arkenvPlugin.

   import arkenvPlugin from "@arkenv/vite-plugin";
   
   export default defineConfig({
     plugins: [arkenvPlugin()],
   });

• Point TanStack add-on dependencies at the current release #1978 888e6c2 @yamcodes

  Scaffolded TanStack Start apps now install @arkenv/core, @arkenv/standard, and @arkenv/vite-plugin at ^1.0.0-rc.2, which matches the versions on npm latest and still accepts 1.0.0 when it publishes.

  Usage:

   npx @tanstack/cli create my-app --add-ons https://arkenv.js.org/tanstack/info.json

@arkenv/standard@1.0.0-rc.3

No changes in this release.

[pkg-pr-new]

Open in StackBlitz

@arkenv/agent-plugin

npm i https://pkg.pr.new/@arkenv/agent-plugin@1982

arkenv

npm i https://pkg.pr.new/arkenv@1982

@arkenv/build

npm i https://pkg.pr.new/@arkenv/build@1982

@arkenv/bun-plugin

npm i https://pkg.pr.new/@arkenv/bun-plugin@1982

@arkenv/core

npm i https://pkg.pr.new/@arkenv/core@1982

@arkenv/fumadocs-ui

npm i https://pkg.pr.new/@arkenv/fumadocs-ui@1982

@arkenv/nextjs

npm i https://pkg.pr.new/@arkenv/nextjs@1982

@arkenv/nuxt

npm i https://pkg.pr.new/@arkenv/nuxt@1982

@arkenv/rsbuild-plugin

npm i https://pkg.pr.new/@arkenv/rsbuild-plugin@1982

@arkenv/standard

npm i https://pkg.pr.new/@arkenv/standard@1982

@arkenv/tanstack-addon

npm i https://pkg.pr.new/@arkenv/tanstack-addon@1982

@arkenv/vite-plugin

npm i https://pkg.pr.new/@arkenv/vite-plugin@1982

commit: a7fe88f