@ingram-tech/nk-dev 0.2.3 → 0.2.4

package/README.md

@@ -15,7 +15,7 @@ vitest, jsdom, jest-dom, knip) as hard dependencies — so one install gives you
 the whole stack instead of re-listing each tool per site.
 
 > **Runtime vs dev-time.** nk-dev is the *dev-time* bundle. Runtime features
-> (`@ingram-tech/email`, `nk-db`, `nk-auth`, …) stay separate packages that
+> (`@ingram-tech/nk-email`, `nk-db`, `nk-auth`, …) stay separate packages that
 > peer-depend on `next`/`react`. See the dev-toolchain carve-out in
 > [`philosophy.md`](https://github.com/ingram-technologies/nextkit/blob/main/docs/philosophy.md).
 

package/guide.md

@@ -9,7 +9,7 @@ package. Stay a thin, standard Next.js app (bun · oxlint + oxfmt · strict TS).
 - **Any form that emails or stores a submission MUST use `@ingram-tech/bot-protection`**
   (server: `verifyHuman` → silently drop bots; client: honeypot + signed token).
   Never ship a form without it.
-- **Send email only via `@ingram-tech/email`** — never add another mail client.
+- **Send email only via `@ingram-tech/nk-email`** — never add another mail client.
 - **Never trust an external request body's shape — validate it with Zod, never
   `as`-cast it.** Every `/api` route and webhook handler takes untrusted input;
   an `as` cast is a lie the type-checker can't catch at runtime.
@@ -71,11 +71,13 @@ the UI/page tree, and never expose internal plumbing under `/api/`.
 
 ## What nextkit provides (reach for these)
 
-- `@ingram-tech/email` — Cloudflare email: `sendEmail`, `fromAddress`
-- `@ingram-tech/nk-auth` — Better Auth foundation: presets you spread into your own `betterAuth()` (mounts at `/auth` via `authBasePath`; org / JWT / passkey / pool / client helpers)
-- `@ingram-tech/nk-db` — Postgres data layer: `createPool` (one TLS-aware pool) + `createQueries` (raw SQL) + `createDb` (Drizzle), plus a PGlite dev/test harness at `@ingram-tech/nk-db/pglite`
+- `@ingram-tech/nk-email` — Cloudflare email: `sendEmail`, `fromAddress`
+- `@ingram-tech/nk-auth` — Better Auth foundation: presets you spread into your own `betterAuth()` (mounts at `/auth` via `authBasePath`; org / JWT / passkey / pool / client helpers). Don't hand-roll session reads or auth middleware — bind `createAuthHelpers` (`getUser` / `requireUser` / `redirectIfAuthenticated`, from `@ingram-tech/nk-auth/server`) and gate routes with the loop-safe `createAuthMiddleware`
+- `@ingram-tech/nk-db` — Postgres data layer: `createPool` (one TLS-aware pool) + `createQueries` (raw SQL) + `createDb` (Drizzle), the PGlite dev/test harness at `@ingram-tech/nk-db/pglite`, the prefixed-id codec at `@ingram-tech/nk-db/id`, and the drift-aware migration runner at `@ingram-tech/nk-db/migrate`
+- `@ingram-tech/nk-api` — the standard HTTP API seam (Hono + `@hono/zod-openapi`): one `{ error, details? }` envelope, `createApiApp` / `createRouter`, auth + multi-tenant resource-scope middleware, pagination helpers, and an emitted OpenAPI/Swagger doc. Reach for it instead of hand-rolling route handlers
+- `@ingram-tech/nk-billing` — Stripe primitives: subscriptions, a Stripe-side wallet, and an optional Postgres credit ledger behind the `/credits` subpath. Prices resolve at runtime by Stripe `lookup_key` — **never hardcode a price id**, so test and live share one code path
 - `@ingram-tech/bot-protection` — invisible form protection (honeypot + timing + Vercel BotID)
-- `@ingram-tech/newsletter` — Supabase newsletter: subscribe / send, 1-click unsubscribe
+- `@ingram-tech/nk-i18n` — type-safe, English-as-key i18n: the English source text *is* the key (no `en.json`), ICU MessageFormat, colocated JSON catalogs; routing is left to the site
 - `@ingram-tech/nk-dev` — the whole dev toolchain in one devDependency: the `nk` command (`nk dev` boots local PGlite via `@ingram-tech/nk-db` if installed, then Next; plus `nk format` / `lint` / `knip` / `check` / `type-check` / `build`), the shared oxlint + oxfmt / TypeScript / Vitest config, knip, the oxfmt format-on-commit hook, and this guide. `nk check` runs every fast checker (oxlint, oxfmt, SQL, knip) in one gate. `nk init` scaffolds a site to use it all.
 
 For detail on any package, read its README in `node_modules/@ingram-tech/<pkg>/`.

package/lib/dev.js

@@ -26,8 +26,8 @@ function hasPgliteDev() {
  * (static/marketing sites with no database). PGlite logic lives in nk-db, not
  * here — `nk` only orchestrates.
  *
- * `nk dev` does not boot local Supabase; the fleet has moved off it. The few
- * Supabase-Postgres holdouts start it themselves until they migrate.
+ * `nk dev` boots no external database service — when nk-db is installed it runs
+ * local PGlite (Postgres-in-WASM), and a site with no database just runs Next.
  */
 export function dev(extraArgs = []) {
 	const command = hasPgliteDev()

package/lib/format.js

@@ -8,14 +8,14 @@ import { run } from "./run.js";
 const require = createRequire(import.meta.url);
 
 // House SQL defaults, used only when the site has no Prettier config of its own
-// (matches the house tab style + Supabase's Postgres dialect).
+// (matches the house tab style + the PostgreSQL dialect).
 const SQL_DEFAULTS = { useTabs: true, language: "postgresql" };
 
 /**
  * `nk format` / `nk format --check`.
  *
  * Code (JS/TS/JSON/CSS) goes through oxfmt; SQL goes through Prettier, which
- * oxfmt can't format. Prettier + prettier-plugin-sql are bundled with nk-cli,
+ * oxfmt can't format. Prettier + prettier-plugin-sql are bundled with nk-dev,
  * so they never appear in any app's dependencies — the "no Prettier for code"
  * rule still holds, it's just the one file type oxfmt lacks.
  */

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@ingram-tech/nk-dev",
-	"version": "0.2.3",
+	"version": "0.2.4",
 	"description": "The nextkit dev toolchain in one package: the `nk` CLI plus shared oxlint/oxfmt, TypeScript, and Vitest config, the format-on-commit hook, and the AI agent guide. `nk init` scaffolds a site to use it.",
 	"license": "MIT",
 	"type": "module",

package/tier-b.json

@@ -5,10 +5,6 @@
 			"error",
 			{
 				"paths": [
-					{
-						"name": "@supabase/supabase-js",
-						"message": "Golden-path data access uses @ingram-tech/nk-db (direct pg + Drizzle), not supabase-js."
-					},
 					{
 						"name": "pg",
 						"importNames": ["Pool", "Client"],