@ingram-tech/nk-dev 0.6.0 → 0.6.1

package/bin/nk.js

@@ -20,7 +20,7 @@ Commands:
   dev                 Start the Next dev server (Turbopack). Boots local PGlite
                       first when @ingram-tech/nk-db is installed (no Docker).
   format [--check]    Format code with oxfmt. --check verifies without writing.
-  lint                Lint with oxlint.
+  lint [...]          Lint with oxlint (extra args passed through, e.g. --fix).
   knip                Find unused dependencies / exports / files with knip.
   ast-grep [...]      Structural search & rewrite of TS/TSX by AST pattern
                       (vendored ast-grep; args passed through). For large
@@ -50,7 +50,7 @@ switch (cmd) {
 		format({ check: rest.includes("--check") });
 		break;
 	case "lint":
-		lint();
+		lint(rest);
 		break;
 	case "knip":
 		knip(rest);

package/lib/dev.js

@@ -1,6 +1,6 @@
 import { spawnSync } from "node:child_process";
 import { createRequire } from "node:module";
-import { resolve } from "node:path";
+import { dirname, resolve } from "node:path";
 
 /**
  * Whether `@ingram-tech/nk-db` is resolvable from the site — the signal that
@@ -19,6 +19,32 @@ function hasPgliteDev() {
 	}
 }
 
+/**
+ * If `@ingram-tech/nk-auth` is installed, the `nk-pglite-dev` flag that makes
+ * the local database apply its shipped auth-table migration chain (see
+ * docs/db-package.md § "The nk-auth migration chain"). Returned as
+ * `--dep-migrations <folder>#<table>` args, or `[]` when nk-auth is absent.
+ *
+ * This resolution lives here, not in nk-db: `nk` is the orchestrator that
+ * already knows both packages, so nk-db's harness stays generic and the
+ * dependency graph stays acyclic (nk-auth → nk-db, never the reverse).
+ */
+function authMigrationArgs() {
+	try {
+		const require = createRequire(resolve(process.cwd(), "package.json"));
+		// Resolve the shipped journal via nk-auth's `./migrations/*` export (its
+		// `exports` deliberately does not expose `./package.json`). A successful
+		// resolve both locates the folder AND confirms the chain is shipped; the
+		// folder is the journal's grandparent (…/migrations/meta/_journal.json).
+		const journal =
+			require.resolve("@ingram-tech/nk-auth/migrations/meta/_journal.json");
+		const folder = dirname(dirname(journal));
+		return ["--dep-migrations", `${folder}#__nkauth_migrations`];
+	} catch {
+		return [];
+	}
+}
+
 /**
  * `nk dev` — start the Next dev server on the golden-path local database.
  *
@@ -33,7 +59,7 @@ function hasPgliteDev() {
  */
 export function dev(extraArgs = []) {
 	const command = hasPgliteDev()
-		? ["nk-pglite-dev", ...extraArgs]
+		? ["nk-pglite-dev", ...authMigrationArgs(), ...extraArgs]
 		: ["next", "dev", "--turbopack", ...extraArgs];
 	if (command[0] === "nk-pglite-dev") {
 		console.log("nk: @ingram-tech/nk-db found — booting local PGlite (no Docker)…");

package/lib/passthrough.js

@@ -4,9 +4,9 @@ import { FORMATTER } from "./formatter.js";
 import { hasKnipConfig, runKnip } from "./knip.js";
 import { run } from "./run.js";
 
-/** `nk lint` — oxlint. */
-export function lint() {
-	process.exit(run(FORMATTER.lint[0], FORMATTER.lint[1]));
+/** `nk lint [...]` — oxlint, with extra args passed through (e.g. `--fix`). */
+export function lint(extraArgs = []) {
+	process.exit(run(FORMATTER.lint[0], [...FORMATTER.lint[1], ...extraArgs]));
 }
 
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@ingram-tech/nk-dev",
-	"version": "0.6.0",
+	"version": "0.6.1",
 	"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",
@@ -49,9 +49,9 @@
 		"@testing-library/jest-dom": "^6.9.1",
 		"@typescript/native": "npm:typescript@^7.0.2",
 		"jsdom": "^29.1.1",
-		"knip": "^6.25.0",
-		"oxfmt": "^0.58.0",
-		"oxlint": "^1.73.0",
+		"knip": "^6.27.0",
+		"oxfmt": "^0.59.0",
+		"oxlint": "^1.74.0",
 		"typescript": "npm:@typescript/typescript6@^6.0.2",
 		"vitest": "^4.1.10"
 	},