@skyf0xx/hedgehog-core-full-stack-app 1.0.13 → 1.1.0

package/README.md

@@ -1,80 +1,57 @@
-# @skyf0xx/hedgehog-core-full-stack-app
+# Hedgehog Full-Stack App Core ⭐
 
-Hedgehog's full-stack-app core: a pre-built, pre-verified Nx/pnpm
-workspace (NestJS + Drizzle + PostgreSQL on the backend, Next.js +
-ShadCN + Tailwind on the frontend, ts-rest contracts, TanStack Query
-hooks) plus the agents, skills, and manifest that drive a Hedgehog
-project built on it.
+### For: Well Architechted Full Stack Apps
 
-## Contents
+Every AI coding tool can scaffold an app. Most let the backend rot as it
+grows: auth logic scattered across routes, contracts drifting from the
+client, schema changes nobody tested.
 
-- `workspace/` — the workspace a Hedgehog install copies to a
-  project's repo root: Nx configuration, `packages/config`,
-  `packages/db`, `apps/api`, `apps/web`, and every enforcement file
-  (lefthook, commitlint, the CI phase gate).
-- `agents/` — `backend-eng`, `ux-planner`, `front-end-eng`.
-- `skills/` — `hedgehog-loop`, `hedgehog-bootstrap`,
-  `hedgehog-bootstrap-full-stack-app-core`, and the Nx tooling skills
-  (`nx-generate`, `nx-run-tasks`, `nx-workspace`,
-  `link-workspace-packages`).
-- `vendor-skills/GSAP` — the vendored asset set `hedgehog-loop`'s
-  build steps reference.
-- `CLAUDE.core.md` — fills a Hedgehog project's root `CLAUDE.md`
-  `{{CORE_SECTION}}` placeholder for this core.
-- `hedgehog-core.yaml` — this package's manifest: name, flag, the
-  selection prose the Hedgehog planner matches a project description
-  against, and which agents/skills/vendor skills it carries.
-- `scripts/regenerate-full-stack-app-core.sh` — the deterministic
-  generator that regenerates `workspace/` from scratch. Run by hand
-  when a workspace dependency needs bumping; not part of any install
-  path.
-- `repro/` — reproductions that drive `workspace/`'s real lefthook
-  configuration and pinned lefthook binary against a real `git commit`,
-  proving the commit gate runs on a fresh install and fails closed when
-  its tooling is missing.
+This core gives Hedgehog a backend that stays honest as it grows: one
+opinionated stack, one enforced build order, and a phase gate that
+blocks the next layer until the current one passes.
 
-## Using this package
+```mermaid
+flowchart LR
+    A[Schema] --> B[Contract]
+    B --> C[Repository]
+    C --> D[Service]
+    D --> E[Controller]
+    E --> F[Hook]
+    F --> G[Screen]
+```
 
-A Hedgehog installation depends on this package for the `full-stack-app`
-core rather than carrying its content directly. See the Hedgehog engine
-(`@skyf0xx/hedgehog`) for the installer and build-graph tooling that
-consumes it.
+## What you get
 
-## Working on this core
+- **NestJS + Drizzle + PostgreSQL** on the backend, **Next.js + ShadCN +
+  Tailwind** on the frontend, locked in once so every feature reuses the
+  same stack.
+- **ts-rest contracts** so the client can't drift from the API: one
+  shared type definition feeds both sides.
+- **TanStack Query hooks**, generated straight from the contracts.
+- **A commit gate** (lefthook + commitlint) that blocks a broken build
+  from ever reaching your history.
 
-This is a versioned npm package that the Hedgehog engine's `init` fetches
-by name, carrying `full-stack-app`'s own agents, skills, a pre-built
-workspace, and the `hedgehog-core.yaml` manifest that names all three to
-the engine. See the engine repo
-([`skyf0xx/hedgehog`](https://github.com/skyf0xx/hedgehog)) and its
-[`ARCHITECTURE.md`](https://github.com/skyf0xx/hedgehog/blob/master/ARCHITECTURE.md)
-for how `init` resolves and fetches a core package — that mechanism lives
-there, not here.
+## Built for production backend work
 
-No root `CLAUDE.md` lives in this repo. `CLAUDE.core.md` is a payload
-file: its content is installed into a *consuming project's* generated
-`CLAUDE.md`, filling that project's `{{CORE_SECTION}}` placeholder. A
-plain root `CLAUDE.md` here would auto-load into any coding agent working
-on this package itself, bleeding project-build context into a repo where
-no Hedgehog build ever runs — build guidance for a project using this
-core lives in that project's own generated `CLAUDE.md`, never here.
+Reach for this core when the project needs authorization beyond
+per-object rules, background jobs, scheduled work, webhooks, or
+server-rendered pages. These are the features that turn "add a database"
+into an ongoing maintenance job.
 
-Changing this core means editing one of: the `workspace/` template (the
-scaffold a Hedgehog install copies into a project's repo root), an agent
-under `agents/`, a skill under `skills/`, or the vendored asset set under
-`vendor-skills/GSAP`. `scripts/regenerate-full-stack-app-core.sh` is the
-deterministic generator that rebuilds `workspace/` from scratch — run it
-by hand after bumping a workspace dependency, then diff the result before
-committing. A change here is a release of this package, not of the
-engine: bump `package.json`'s version, commit, and merge to `main` — this
-repo's own `publish.yml` tags and publishes from there.
+## Easy to install and use
 
-When `workspace/`'s template needs a new piece of repeatable boilerplate
-— a new module shape, a new generated file type — prefer building or
-extending a generator over hand-authoring the output once. This core
-already models the pattern: `workspace/tools/generators/` carries Nx
-generators for every domain-module layer (`schema`, `contract`,
-`repository`, `service`, `controller`, `hook`, `screen`) that
-`nx-generate` drives instead of an agent writing that boilerplate
-freehand. Other cores and future add-ons should model new scaffolding
-against this one.
+Ask your agent:
+*"Install Hedgehog and build me a [your app idea]"*
+
+<details>
+<summary>For your agent</summary>
+
+```
+npx @skyf0xx/hedgehog init
+```
+
+```
+npx @skyf0xx/hedgehog init --ts-full-stack-app
+```
+
+Technical details: [ARCHITECTURE.md](ARCHITECTURE.md)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyf0xx/hedgehog-core-full-stack-app",
-  "version": "1.0.13",
+  "version": "1.1.0",
   "description": "Hedgehog's full-stack-app core: an Nx/pnpm/NestJS/Next.js workspace, backend-first domain module build discipline, and the agents and skills that drive it.",
   "type": "module",
   "scripts": {

package/skills/hedgehog-bootstrap/SKILL.md

@@ -163,9 +163,14 @@ write — same treatment as an out-of-scope `apps/mobile`.
 
 ```bash
 npx nx g @nx/js:lib packages/auth --bundler=none --unitTestRunner=vitest
-pnpm add better-auth @thallesp/nestjs-better-auth
 ```
 
+`better-auth` and `@thallesp/nestjs-better-auth` are already declared in
+root `package.json` and resolved by `pnpm-lock.yaml` — the core ships
+them, so there is nothing to install here. Don't run `pnpm add` for
+either: an add resolves against npm at whatever is latest today, which
+is the drift this core pins them to avoid.
+
 Configure the Drizzle adapter against `packages/db`. Add
 `BETTER_AUTH_SECRET: z.string().min(32)` to `packages/config/env.schema.ts`
 now (it doesn't exist in the core schema `hedgehog-bootstrap-full-stack-app-core`
@@ -175,9 +180,10 @@ line reproduces the exact `loadEnv()` crash-on-boot that
 `hedgehog-bootstrap-full-stack-app-core`'s `DATABASE_URL` entry exists to prevent, just
 for this var instead. Tag: `scope:auth`, `type:adapter`.
 
-Also wire the global auth guard on `apps/api`: `pnpm add
-@thallesp/nestjs-better-auth` there too and register the guard
-(secure-by-default) against `packages/auth`. `apps/api`'s
+Also wire the global auth guard on `apps/api`: register the guard
+(secure-by-default) against `packages/auth` — the root declaration
+already resolves `@thallesp/nestjs-better-auth` for every project in the
+workspace, so `apps/api` needs no add of its own. `apps/api`'s
 `depConstraints` entry needs `scope:auth` added to its allowed
 dependencies now — the one deliberate exception to "api reaches things
 only through ports," since auth is cross-cutting infra, not a domain
@@ -195,9 +201,12 @@ skipped, say so plainly and move on — same treatment as an out-of-scope
 
 ```bash
 npx nx g @nx/node:app apps/worker
-pnpm add bullmq ioredis
 ```
 
+`bullmq` and `ioredis` are already declared in root `package.json` and
+resolved by `pnpm-lock.yaml` — same as Auth's packages above. Nothing to
+install here; don't run `pnpm add` for either.
+
 Add a `redis` service to the root `docker-compose.yml` that
 `hedgehog-bootstrap-full-stack-app-core` landed (Postgres-only) and
 `REDIS_URL: z.string().url()` to `packages/config/env.schema.ts` (it
@@ -235,12 +244,49 @@ Skip this step entirely if Mobile isn't on for this project (check
 say so plainly and move on — same pattern as Auth (step 1) and Queue
 (step 2) when their add-on is off.
 
+Mobile's packages are pinned in `addon-versions.json` at the workspace
+root, not named inline here and not declared in root `package.json` —
+Expo pulls a native build matrix that has no business in a project that
+never scaffolds `apps/mobile`. Read every version from that file rather
+than typing one, so this step installs what the core was last gated
+against:
+
 ```bash
+NX_EXPO=$(node -p "require('./addon-versions.json').mobile['@nx/expo']")
+NATIVEWIND=$(node -p "require('./addon-versions.json').mobile.nativewind")
+RNR=$(node -p "require('./addon-versions.json').mobile['@react-native-reusables/cli']")
+
+pnpm add -w -D "@nx/expo@$NX_EXPO"
+pnpm add -w "nativewind@$NATIVEWIND"
+
 npx nx g @nx/expo:app apps/mobile --unitTestRunner=jest
-npx @react-native-reusables/cli@latest init
-npx @react-native-reusables/cli@latest add button text
+
+npx "@react-native-reusables/cli@$RNR" init
+npx "@react-native-reusables/cli@$RNR" add button text
 ```
 
+`-w` is required: this is a pnpm workspace, and an add without it fails
+with `ERR_PNPM_ADDING_TO_ROOT` rather than installing.
+
+`@nx/expo:app` generates `apps/mobile/src/test-setup.ts` with an untyped
+`defineGlobal` helper, which is a `TS7006` error under the core's
+`strict: true` base tsconfig — `mobile:typecheck` fails on a fresh
+scaffold until it is annotated:
+
+```ts
+const defineGlobal = (name: string, value: unknown) => {
+```
+
+Make that edit before the step's commit. `nx-migrate.yml`'s add-on gate
+applies the same annotation, so the day `@nx/expo` ships the types both
+stop being needed together.
+
+`@nx/expo`'s pin is byte-identical to every other `@nx/*` entry in root
+`package.json` — Nx requires its plugin matrix to be version-identical,
+and a mismatch fails at generator time with a resolution error rather
+than at install. If the pin and the `@nx/*` entries have drifted apart,
+stop and fix `addon-versions.json` rather than installing anyway.
+
 `@nx/expo:app`'s own default for `--unitTestRunner` is `none` — pass it
 explicitly, or `apps/mobile` has no `test` target at all and the `screen`
 layer's verify command below fails on a missing target rather than a
@@ -253,7 +299,7 @@ NativeWind and the `@/*` path alias into `apps/mobile/tsconfig.json`
 named components' source into `apps/mobile/src/components/ui/`. `button`
 and `text` are the two the `screen` generator's mobile output imports —
 add any further components `front-end-eng` needs the same way, per
-module, as it builds.
+module, as it builds, at the same pinned CLI version.
 
 Edit `init`'s generated theme (`tailwind.config.js` colors, light/dark)
 to match `apps/web`'s base theme (landed by
@@ -355,6 +401,19 @@ time via `hedgehog next`/`hedgehog verify`, each its own commit.
   (written by `planner` at planning intake) turns that add-on on — say so
   plainly and skip otherwise, don't leave it ambiguous whether the step
   was considered.
+- A skipped Auth or Queue step leaves that add-on's packages declared but
+  unused, since the core ships them in root `package.json`. Delete the
+  skipped add-on's entries (`better-auth` and
+  `@thallesp/nestjs-better-auth` for Auth; `bullmq` and `ioredis` for
+  Queue) and re-run `pnpm install` so the lockfile drops them. Do this in
+  the same commit that records the skip. Mobile needs nothing — its
+  packages were never in the install to begin with.
+- Never write a version number into a command in this file. Auth and
+  Queue versions come from root `package.json`; Mobile's come from
+  `addon-versions.json`. A version typed into a step is invisible to
+  `nx migrate`, to `pnpm outdated`, and to CI's add-on gate, so it drifts
+  silently in whichever direction the day's npm resolution happens to
+  take it.
 - Don't add domain schema, contracts, or any `libs/<module>/*` content —
   that's Phase A, started after Bootstrap, one module at a time.
 - Don't deviate from the package/library choices above, for whichever

package/skills/hedgehog-loop/SKILL.md

@@ -153,20 +153,42 @@ writes `docs/design/<module>.md`, not its own compiled layer — the
    zero. `hedgehog ready` previews the same decision without claiming
    anything — CLAIMABLE vs HELD BACK, with the reason for each holdback —
    useful for understanding the scheduler before committing to a claim.
-2. **Dispatch each claimed packet to its own subagent** — `backend-eng`
-   (Phase A) or `front-end-eng` (Phase B), matching each packet's ALLOWED
-   SCOPE — in ONE message with parallel tool calls, not one agent call
-   after another. This is a Claude session orchestrating via the Agent
-   tool's parallel-call mechanism: N claimed tasks means N Agent calls in
-   the same message. If a dispatch by name reports the agent as not
-   found — expected right after `init`/`update` installed it this same
+2. **For each claimed packet, decide inline vs. dispatch, then act.**
+   Default to dispatching to its own subagent — `backend-eng` (Phase A)
+   or `front-end-eng` (Phase B), matching the packet's ALLOWED SCOPE —
+   in ONE message with parallel tool calls, not one agent call after
+   another. This is a Claude session orchestrating via the Agent tool's
+   parallel-call mechanism: N claimed tasks dispatched this way means N
+   Agent calls in the same message. Build or confirm the packet
+   directly instead, with no subagent, only when the packet clears one
+   of these from the packet alone:
+   - **ALLOWED SCOPE** names a small, bounded set of files the
+     orchestrator can read directly without ballooning its own context.
+   - **RELEVANT RULES or the module name** make the layer's irrelevance
+     checkable in one read — the task's own rules describe a concern
+     that plainly doesn't touch this layer's area.
+   - The change, once its shape is known, is small and mechanical — a
+     rename, an import fix, a one-line registration — rather than
+     something needing a subagent's isolated, fresh-context judgment.
+
+   Escalate to a full `backend-eng`/`front-end-eng` dispatch mid-layer
+   the moment any of these turns out false — a "quick check" that
+   surfaces real cross-file reasoning, an unclear scope, or a diff
+   bigger than expected. Never lock in "inline" once guessed. Either
+   way, the layer's own VERIFICATION command and ALLOWED SCOPE gate
+   apply identically in step 4 — this choice changes who reads, writes,
+   and checks, never what gets checked before it's accepted. A no-op
+   found inline is still reported per the packet's HONESTY rules, never
+   assumed. If a dispatch by name reports the agent as not found —
+   expected right after `init`/`update` installed it this same
    session — see root CLAUDE.md's "Delegating on this host" note rather
    than treating it as fatal.
-3. Each agent **runs typecheck/lint/test on its own work** (mirrors
-   lefthook, wired at bootstrap) as a sanity check before reporting
-   back — necessary, not sufficient. Per task, per agent: the agent
-   reports its work as done; it does not move the task and does not
-   commit.
+3. Whoever built the packet — the dispatched agent, or the orchestrator
+   itself when it went inline — **runs typecheck/lint/test on that
+   work** (mirrors lefthook, wired at bootstrap) as a sanity check
+   before reporting back — necessary, not sufficient. Per task: the
+   work is reported as done; the task is not moved and nothing is
+   committed yet.
 4. **As each report arrives, verify it — one at a time, serially.** Run
    `hedgehog verify <task-id> --owner <owner>` (the same owner that
    claimed it; verify requires the lease owner). Building happens in

package/workspace/addon-versions.json

@@ -0,0 +1,39 @@
+{
+  "$comment": [
+    "Pinned versions for the Mobile add-on's packages, which are NOT declared in",
+    "workspace/package.json. Expo pulls a native build matrix (Metro, the",
+    "React Native toolchain, the @react-native-reusables CLI's own tree) that",
+    "every consuming project would otherwise install whether or not it ever",
+    "scaffolds apps/mobile. Declaring them here keeps the version a tracked,",
+    "tool-visible fact — nx-migrate.yml's add-on gate scaffolds against these",
+    "pins every Monday, and a bump is a reviewable diff — without putting the",
+    "matrix in the default install.",
+    "",
+    "Auth and Queue packages are NOT here: they are plain Node dependencies with",
+    "no native matrix, so they are declared in workspace/package.json and",
+    "resolved by pnpm-lock.yaml like every other core dependency.",
+    "",
+    "@nx/expo must stay byte-identical to every other @nx/* entry in",
+    "workspace/package.json — Nx requires its plugin matrix to be version-",
+    "identical, and a mismatch fails at generator time, not install time.",
+    "nx-migrate.yml's add-on gate asserts that equality before it scaffolds.",
+    "",
+    "nativewind stays on 4.x: 5.x, the line that targets Tailwind v4, is still",
+    "a preview release. 4.x declares a `tailwindcss@~3` peer (through",
+    "react-native-css-interop) against the v4 that apps/web pins, which the",
+    "`react-native-css-interop>tailwindcss` peerDependencyRules entry in",
+    "package.json accepts — apps/mobile carries its own NativeWind-side Tailwind",
+    "config, written by the @react-native-reusables CLI's init, so the two",
+    "never share a config. Revisit both when nativewind 5 goes stable.",
+    "",
+    "@react-native-reusables/cli is a scaffolder, not a runtime dependency — it",
+    "copies component source into apps/mobile and is never installed. Pinning it",
+    "is what stops `npx @react-native-reusables/cli@latest` from resolving to a",
+    "different generator on every Bootstrap run."
+  ],
+  "mobile": {
+    "@nx/expo": "23.1.2",
+    "nativewind": "4.2.6",
+    "@react-native-reusables/cli": "0.7.1"
+  }
+}

package/workspace/apps/api/package.json

@@ -46,11 +46,23 @@
         "executor": "@nx/js:prune-lockfile",
         "outputs": [
           "{workspaceRoot}/apps/api/dist/package.json",
-          "{workspaceRoot}/apps/api/dist/pnpm-lock.yaml"
+          "{workspaceRoot}/apps/api/dist/pnpm-lock.yaml",
+          "{workspaceRoot}/apps/api/dist/pnpm-workspace.yaml",
+          "{workspaceRoot}/apps/api/dist/patches",
+          "{workspaceRoot}/apps/api/dist/local_path_modules"
         ],
         "options": {
           "buildTarget": "build"
-        }
+        },
+        "inputs": [
+          "default",
+          "^default",
+          "{workspaceRoot}/pnpm-workspace.yaml",
+          "{workspaceRoot}/package.json",
+          {
+            "runtime": "node -e \"try{console.log('pnpm major '+require('child_process').execSync('pnpm --version',{stdio:['ignore','pipe','ignore']}).toString().trim().split('.')[0])}catch{console.log('pnpm major unavailable')}\""
+          }
+        ]
       },
       "copy-workspace-modules": {
         "dependsOn": [

package/workspace/apps/api/vitest.config.mts

@@ -1,7 +1,7 @@
 import { defineConfig } from 'vitest/config';
 
 export default defineConfig(() => ({
-  root: __dirname,
+  root: import.meta.dirname,
   cacheDir: '../../node_modules/.vite/apps/api',
   test: {
     name: 'api',

package/workspace/apps/api-e2e/vitest.config.mts

@@ -1,7 +1,7 @@
 import { defineConfig } from 'vitest/config';
 
 export default defineConfig(() => ({
-  root: __dirname,
+  root: import.meta.dirname,
   cacheDir: '../../node_modules/.vite/apps/api-e2e',
   test: {
     name: 'api-e2e',

package/workspace/apps/web/AGENTS.md

@@ -0,0 +1,9 @@
+<!-- BEGIN:nextjs-agent-rules -->
+
+# This is NOT the Next.js you know
+
+This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in `node_modules/next/dist/docs/` (resolved from this file's directory; in monorepos the `next` package may not be visible from the repo root) before writing any code. Heed deprecation notices.
+
+This block is written and re-added by `next dev` — verify at `node_modules/next/dist/server/lib/generate-agent-files.js`. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree clean.
+
+<!-- END:nextjs-agent-rules -->

package/workspace/apps/web/CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

package/workspace/apps/web/next-env.d.ts

@@ -1,7 +1,7 @@
 /// <reference types="next" />
 /// <reference types="next/image-types/global" />
-import "./.next/types/routes.d.ts";
-import "./.next/types/root-params.d.ts";
+import "./.next/dev/types/routes.d.ts";
+import "./.next/dev/types/root-params.d.ts";
 
 // NOTE: This file should not be edited
 // see https://nextjs.org/docs/app/api-reference/config/typescript for more information.

package/workspace/apps/web/vitest.config.mts

@@ -3,7 +3,7 @@ import react from '@vitejs/plugin-react';
 import { fileURLToPath } from 'node:url';
 
 export default defineConfig(() => ({
-  root: __dirname,
+  root: import.meta.dirname,
   cacheDir: '../../node_modules/.vite/apps/web',
   plugins: [react()],
   resolve: {

package/workspace/package.json

@@ -14,17 +14,17 @@
     "@nestjs/schematics": "^11.0.0",
     "@nestjs/testing": "^11.0.0",
     "@next/eslint-plugin-next": "^16.1.6",
-    "@nx/devkit": "23.1.2",
-    "@nx/eslint": "23.1.2",
-    "@nx/eslint-plugin": "23.1.2",
-    "@nx/js": "23.1.2",
-    "@nx/nest": "23.1.2",
-    "@nx/next": "23.1.2",
-    "@nx/node": "23.1.2",
-    "@nx/playwright": "23.1.2",
-    "@nx/vitest": "23.1.2",
-    "@nx/web": "23.1.2",
-    "@nx/webpack": "23.1.2",
+    "@nx/devkit": "23.2.0",
+    "@nx/eslint": "23.2.0",
+    "@nx/eslint-plugin": "23.2.0",
+    "@nx/js": "23.2.0",
+    "@nx/nest": "23.2.0",
+    "@nx/next": "23.2.0",
+    "@nx/node": "23.2.0",
+    "@nx/playwright": "23.2.0",
+    "@nx/vitest": "23.2.0",
+    "@nx/web": "23.2.0",
+    "@nx/webpack": "23.2.0",
     "@playwright/test": "^1.37.0",
     "@swc-node/register": "~1.11.1",
     "@swc/cli": "~0.8.1",
@@ -52,7 +52,7 @@
     "eslint-plugin-react-hooks": "7.1.1",
     "jsdom": "^30.0.1",
     "lefthook": "^2.1.10",
-    "nx": "23.1.2",
+    "nx": "23.2.0",
     "prettier": "~3.6.2",
     "tslib": "^2.3.0",
     "typescript": "~6.0.3",
@@ -67,8 +67,12 @@
     "@nestjs/common": "^11.0.0",
     "@nestjs/core": "^11.0.0",
     "@nestjs/platform-express": "^11.0.0",
+    "@thallesp/nestjs-better-auth": "^2.7.0",
     "axios": "^1.18.0",
+    "better-auth": "^1.7.2",
+    "bullmq": "^6.3.4",
     "drizzle-orm": "^0.45.2",
+    "ioredis": "^6.0.0",
     "nestjs-pino": "^4.6.1",
     "next": "~16.3.0",
     "pg": "^8.22.0",
@@ -88,11 +92,12 @@
         "eslint-plugin-import>eslint": "10",
         "eslint-plugin-jsx-a11y>eslint": "10",
         "eslint-plugin-react>eslint": "10",
-        "@exodus/bytes>@noble/hashes": "1"
+        "@exodus/bytes>@noble/hashes": "1",
+        "react-native-css-interop>tailwindcss": "4"
       }
     },
     "overrides": {
-      "@nx/module-federation": "23.1.2",
+      "@nx/module-federation": "23.2.0",
       "esbuild": "0.25.12",
       "axios": "^1.18.0",
       "brace-expansion@1": "^1.1.18",

package/workspace/packages/config/vitest.config.mts

@@ -1,7 +1,7 @@
 import { defineConfig } from 'vitest/config';
 
 export default defineConfig(() => ({
-  root: __dirname,
+  root: import.meta.dirname,
   cacheDir: '../../node_modules/.vite/packages/config',
   test: {
     name: 'config',

package/workspace/packages/db/vitest.config.mts

@@ -1,7 +1,7 @@
 import { defineConfig } from 'vitest/config';
 
 export default defineConfig(() => ({
-  root: __dirname,
+  root: import.meta.dirname,
   cacheDir: '../../node_modules/.vite/packages/db',
   test: {
     name: 'db',