Skip to content
Shaun Nguyen
writing February 02, 2026 • 1 MIN READ

Setup NextJS debug on VSCode Windows + MS Edge

A guide to setting up NextJS debugging on Visual Studio Code using Windows and Microsoft Edge.

#nextjs #vscode #debugging #windows #msedge

Table of Contents

Damn, I got stucked when following NextJS recommendation, because it only work on UNIX-like system which have shell that can run .sh file. Totally bullshit.

This instruction prefer Bun, because it is Typescript native and spin up dev quick. You can choose NPM or Yarn, or PNPM as your favorite package manager.

After some conversation with Claude, I figure it out by edit the program part of Next.js: debug full stack to direct next executable.

This is .vscode/launch.json code for lazy person:

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Next.js: debug server-side",
      "type": "node-terminal",
      "request": "launch",
      "command": "bun dev"
    },
    {
      "name": "Next.js: debug client-side",
      "type": "msedge",
      "request": "launch",
      "url": "http://localhost:3000"
    },
    {
      "name": "Next.js: debug full stack",
      "type": "node",
      "request": "launch",
      "program": "${workspaceFolder}/node_modules/next/dist/bin/next",
      "args": [
        "dev"
      ],
      "runtimeArgs": [
        "--inspect"
      ],
      "skipFiles": [
        "<node_internals>/**"
      ],
      "serverReadyAction": {
        "action": "debugWithEdge",
        "killOnServerStop": true,
        "pattern": "- Local:\\s+(https?://\\S+)",
        "uriFormat": "%s",
        "webRoot": "${workspaceFolder}"
      },
      "env": {
        "NODE_OPTIONS": "--inspect"
      },
      "console": "internalConsole",
      // "outputCapture": "std"
    }
  ]
}

Explore Topics

#Debugging (1) #Development (1) #Electron (1) #Linux (1) #Msedge (1) #Nextjs (1) #Vscode (1) #Windows (1) #Wine (1) #Zalo (1)