Node flags legacy url.parse() (DEP0169) as having security implications and recommends the WHATWG URL API instead. The main request handler's parsedUrl argument to Next's handle() is optional and unused by us, so that call is dropped entirely (matching Next's own minimal custom-server example); the WS upgrade path-check now uses `new URL()` instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
TriggerShell web app
This is the Next.js app that TriggerShell's Python CLI (triggershell dev / triggershell start)
launches — it's not meant to be run standalone with next dev/next start since it needs a
custom server (server.ts) for the WebSocket endpoint.
See the repo root README for how to run TriggerShell end-to-end, and
../docs/ARCHITECTURE.md for how this app is put together.
pnpm install
pnpm dev # tsx watch server.ts - reads TRIGGERSHELL_CONFIG_PATH from the environment
pnpm lint
pnpm typecheck
pnpm db:studio # browse the SQLite database