Labels.io

Troubleshooting

The few things that actually go wrong, and the one-line fixes.

The all-purpose fix: tell your AI "it is not working" and paste the error. The get-it-running.md skill covers recovery, not just first install. For the common cases:

Port already in use

Another dev server is squatting on 3000:

pnpm dev --port 3001

pnpm: command not found

corepack enable

Ships with Node 16.13+; it activates pnpm without a global install.

Node too old

The kit needs Node 20+. Check with node -v, upgrade via nodejs.org or your version manager.

Route changes not showing up

app/routeTree.gen.ts regenerates while pnpm dev is running. If routes look stale, restart the dev server; never edit that file by hand.

A wired feature stopped working

Check .env first: every wire-* skill lists the variables it added. A missing key fails quietly on mock-looking screens.

Still stuck?

Run grep -rn "🔌 INTEGRATION" app/ to see what is still mock; half of all "bugs" are a screen that was never wired in the first place.

On this page