Skip to content

chore: add VS Code launch config for debugging#15

Open
avdev4j wants to merge 1 commit into
mainfrom
chore/vscode-launch-config
Open

chore: add VS Code launch config for debugging#15
avdev4j wants to merge 1 commit into
mainfrom
chore/vscode-launch-config

Conversation

@avdev4j

@avdev4j avdev4j commented Jul 6, 2026

Copy link
Copy Markdown

What

Adds .vscode/launch.json with two Next.js debug configurations:

  • Next.js: debug server-side — launches npm run dev -- --inspect with the Node inspector attached, so server-side code (API routes, validators) can be debugged with breakpoints.
  • Next.js: debug full stack — launches the Next binary with --inspect and auto-opens the browser for combined server + client debugging.

Why

Makes it possible to set breakpoints and step through server-side code (e.g. lesson validators) locally in VS Code.

Scope

Tooling/developer-experience only. No changes to application or business logic. Config taken from the official Next.js debugging guide for this version.

@vercel

vercel Bot commented Jul 6, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
liftoff Ready Ready Preview, Comment Jul 6, 2026 7:49am

Request Review

Adds .vscode/launch.json with server-side and full-stack Next.js debug configurations so the dev server can be launched with the Node inspector attached. Tooling only; no changes to application or business logic.

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant