@slip-stream-kit/config

The config-authoring surface for infra-kit. Depends on zod and nothing else.

Why this package exists

It is not a convenience split — it is the only way infra-kit can be a global CLI.

Three facts force it:

1. Node ESM cannot resolve a bare specifier from a global install. NODE_PATH is ignored by ESM. So import { defineConfig } from 'infra-kit' in an infra-kit.config.ts, and import { infraKitDev } from 'infra-kit/vite' in a vite.config.ts, each force infra-kit to be a local dependency. Both tsc --noEmit and vite (a separate process) demand it.
2. npm cannot install a package's exports without its bin.
3. A local node_modules/.bin/infra-kit shadows the global one.

Together: while configs imported from infra-kit, a local install was mandatory, and that local install hijacked every pnpm exec infra-kit call — so npm i -g infra-kit was inert, and every consumer repo carried the CLI's full dependency tree (fastify, ink, react, chokidar, zx, …) just to call an identity function.

The bin-bearing package and the locally-resolved package must therefore be two different npm packages. This is the locally-resolved one. Install it as a devDependency; install infra-kit globally.

Usage

// infra-kit.config.ts
import { defineConfig } from '@slip-stream-kit/config'

export default defineConfig(() => ({ requiredScripts: [], requiredFiles: [] }))

// vite.config.ts
import { infraKitDev } from '@slip-stream-kit/config/vite'
import { defineConfig } from 'vite'

export default defineConfig(async ({ command }) => ({
  // Per-worktree dynamic dev port + the config-driven `dev.proxy`. Passing `command` makes it a
  // no-op for `build`.
  server: await infraKitDev({ command }),
}))

@slip-stream-kit/vite wraps that helper as a vite plugin (plugins: [infraKit()]) and adds what the helper cannot do: it re-resolves the proxy while the server is up, so a backend started after the frontend flips its route from cloud to local on its own. The helper here stays supported — use it when you want the raw server block.

// vendor.config.ts
import { defineVendorConfig } from '@slip-stream-kit/config'

export default defineVendorConfig({ copy: [] })

Entry points

| Entry | Contents | | --- | --- | | . | defineConfig, defineVendorConfig, and the config types | | ./vite | infraKitDev, infraKitProxy, resolveProxyConfig, slugifyRelease | | ./internal | Consumed by the infra-kit CLI. Not public API — no stability guarantee |

Versioning

Released in lockstep with infra-kit: the two share the same version line, always.

This is load-bearing, not cosmetic. The CLI self-updates silently on developer machines while this package stays pinned in each consumer's lockfile, so a new CLI routinely meets an older helper. The CLI guards that skew by comparing this package's version against a floor — a guard that only works while both sides are points on the same version line. An independent version line here would make the floor either reject every consumer or pass vacuously, and a vacuous pass silently reinstates the failure the floor exists to prevent.