Add structured backend logging with pino
CI / Checks (push) Successful in 47s
CI / Publish to npm registry (push) Successful in 50s

Wires leveled, structured logging (pretty in dev, JSON in prod) through
the server lifecycle, HTTP/WS request handling, run engine, auth, db,
and config loading. CLI command output is left untouched since it's
user-facing terminal UX, not backend logs.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
2026-08-19 09:54:16 +02:00
co-authored by Claude Sonnet 5
parent 3272b9db76
commit 96a66fc857
13 changed files with 420 additions and 16 deletions
+3 -1
View File
@@ -1,6 +1,6 @@
{
"name": "triggershell",
"version": "0.1.0",
"version": "1.0.4",
"license": "MIT",
"type": "module",
"repository": {
@@ -60,6 +60,7 @@
"lucide-react": "^1.31.0",
"next": "16.3.1",
"next-themes": "^0.4.6",
"pino": "^10.3.1",
"react": "19.2.8",
"react-dom": "19.2.8",
"react-hook-form": "^7.85.0",
@@ -86,6 +87,7 @@
"drizzle-kit": "^0.31.10",
"eslint": "^9",
"eslint-config-next": "16.3.1",
"pino-pretty": "^13.1.3",
"prettier": "^3.9.6",
"prettier-plugin-tailwindcss": "^0.8.1",
"tailwindcss": "^4",