$ pnpm --filter @zoen/admin build
# cwd /Users/king/Desktop/Workspace/SRO/zoen
# exit 0


> @zoen/admin@0.1.0 build /Users/king/Desktop/Workspace/SRO/zoen/apps/admin
> node ../../tools/web/sync-ui-assets.mjs && NEXT_TELEMETRY_DISABLED=1 next build

✔ sync-ui-assets: 119 sprites + brand ready (0 copied)
▲ Next.js 16.3.8 (Turbopack)
- Environments: .env.local
✓ Running next.config.ts took 15ms
- Experiments (use with caution):
  · serverActions

  Creating an optimized production build ...
✓ Compiled successfully in 1766ms
  Running TypeScript ...
  Finished TypeScript in 2.1s ...
  Collecting page data using 7 workers ...
  Generating static pages using 7 workers (0/47) ...
  Generating static pages using 7 workers (11/47) 
  Generating static pages using 7 workers (23/47) 
  Generating static pages using 7 workers (35/47) 
✓ Generating static pages using 7 workers (47/47) in 262ms
  Finalizing page optimization ...

Route (app)
┌ ƒ /
├ ƒ /_not-found
├ ƒ /account
├ ƒ /ai
├ ƒ /ai/[id]
├ ƒ /api/admin/q
├ ○ /apple-icon.png
├ ƒ /approvals
├ ƒ /bugs
├ ƒ /bugs/[id]
├ ƒ /bugs/intake
├ ƒ /config
├ ƒ /growth
├ ƒ /growth/funnels
├ ƒ /growth/waves
├ ○ /icon.png
├ ƒ /live
├ ƒ /login
├ ƒ /login/accept
├ ƒ /login/enroll
├ ƒ /login/verify
├ ○ /manifest.webmanifest
├ ƒ /players
├ ƒ /players/[id]
├ ƒ /players/characters/[cid]
├ ƒ /production
├ ƒ /production/art
├ ƒ /production/roadmap
├ ƒ /production/tasks
├ ƒ /production/tokens
├ ƒ /releases
├ ƒ /security
├ ƒ /security/appeals
├ ƒ /security/devices
├ ƒ /security/reports
├ ƒ /security/rules
├ ƒ /support
├ ƒ /support/[id]
├ ƒ /system/audit
├ ƒ /system/health
├ ƒ /system/integrations
├ ƒ /system/roles
├ ƒ /system/staff
├ ƒ /website
├ ƒ /website/faq
├ ƒ /website/posts/[id]
├ ƒ /website/settings
├ ƒ /website/status
├ ƒ /world
├ ƒ /world/drops
└ ƒ /world/economy


ƒ Proxy (Middleware)

○  (Static)   prerendered as static content
ƒ  (Dynamic)  server-rendered on demand

Turbopack build encountered 3 warnings:
./apps/admin/lib/repo.ts:36:25
Warning: Dynamic filesystem access causes tracing of the whole project
  34 |   if (hit?.mtime === mtime) return hit.value as T;
  35 |   try {
> 36 |     const value = parse(fs.readFileSync(file, 'utf8'));
     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  37 |     cache.set(key, { mtime, value });
  38 |     return value;
  39 |   } catch { return null; }

Static analysis determined that this filesystem access causes the whole project to be traced and included in the output.
This is usually unintentional and leads to all source files (including the public folder) to be deployed as part of the server code.
This can slow down deployments or lead to failures when size limits are exceeded.
To resolve this, you can
- make sure the path is statically scoped to some subfolder, for example path.join(process.cwd(), 'data', bar), or
- only use them in development, or
- opt out by adding an ignore comment to the highlighted call: fs.readFileSync(/*turbopackIgnore: true*/ ...), or
- remove them.

Import trace:
  Server Component:
    ./apps/admin/lib/repo.ts
    ./apps/admin/app/(console)/production/tasks/page.tsx


./apps/admin/lib/repo.ts:32:17
Warning: Dynamic filesystem access causes tracing of the whole project
  30 |   const file = path.join(r, FILES[key]);
  31 |   let mtime: number;
> 32 |   try { mtime = fs.statSync(file).mtimeMs; } catch { return null; }
     |                 ^^^^^^^^^^^^^^^^^
  33 |   const hit = cache.get(key);
  34 |   if (hit?.mtime === mtime) return hit.value as T;
  35 |   try {

Static analysis determined that this filesystem access causes the whole project to be traced and included in the output.
This is usually unintentional and leads to all source files (including the public folder) to be deployed as part of the server code.
This can slow down deployments or lead to failures when size limits are exceeded.
To resolve this, you can
- make sure the path is statically scoped to some subfolder, for example path.join(process.cwd(), 'data', bar), or
- only use them in development, or
- opt out by adding an ignore comment to the highlighted call: fs.statSync(/*turbopackIgnore: true*/ ...), or
- remove them.

Import trace:
  Server Component:
    ./apps/admin/lib/repo.ts
    ./apps/admin/app/(console)/production/tasks/page.tsx


./apps/admin/lib/repo.ts:30:16
Warning: Dynamic filesystem access causes tracing of the whole project
  28 |   const r = root();
  29 |   if (!r) return null;
> 30 |   const file = path.join(r, FILES[key]);
     |                ^^^^^^^^^^^^^^^^^^^^^^^^
  31 |   let mtime: number;
  32 |   try { mtime = fs.statSync(file).mtimeMs; } catch { return null; }
  33 |   const hit = cache.get(key);

Static analysis determined that this filesystem access causes the whole project to be traced and included in the output.
This is usually unintentional and leads to all source files (including the public folder) to be deployed as part of the server code.
This can slow down deployments or lead to failures when size limits are exceeded.
To resolve this, you can
- make sure the path is statically scoped to some subfolder, for example path.join(process.cwd(), 'data', bar), or
- only use them in development, or
- opt out by adding an ignore comment to the highlighted call: path.join(/*turbopackIgnore: true*/ ...), or
- remove them.

Import trace:
  Server Component:
    ./apps/admin/lib/repo.ts
    ./apps/admin/app/(console)/production/tasks/page.tsx