Part of EPIC #698.
The scaffolded docker-compose maps port 9229 for the GraalVM Chrome inspector, but nothing ships to use it: no .vscode/launch.json (the scaffold does ship extensions.json/settings.json), no debugging guide in the docs. On a stock instance nothing listens until the debugger is configured. The de facto workflow is console.* + docker compose logs -f jahia.
For comparison, Astro debugging is stock Node tooling: node --inspect, every IDE attaches, sourcemaps just work.
Proposal:
- Ship a
launch.json in the scaffold with an attach configuration for the JS inspector (and document any engine property needed to enable the debug listener).
- Add a "Debugging" page to the getting-started docs: attach from VS Code / Chrome DevTools, breakpoints in
.server.tsx, sourcemap expectations, and the log-tailing fallback.
Part of EPIC #698.
The scaffolded docker-compose maps port 9229 for the GraalVM Chrome inspector, but nothing ships to use it: no
.vscode/launch.json(the scaffold does shipextensions.json/settings.json), no debugging guide in the docs. On a stock instance nothing listens until the debugger is configured. The de facto workflow isconsole.*+docker compose logs -f jahia.For comparison, Astro debugging is stock Node tooling:
node --inspect, every IDE attaches, sourcemaps just work.Proposal:
launch.jsonin the scaffold with an attach configuration for the JS inspector (and document any engine property needed to enable the debug listener)..server.tsx, sourcemap expectations, and the log-tailing fallback.