segment-boneyard/nightmare

vscode debugging nightmare - launch.json

Open

#1,341 opened on Dec 12, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (1,076 forks)batch import
Help Wanted

Repository metrics

Stars
 (19,507 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I'm using vscode, typescript and nightmarejs.

Since node v8, inspector debugging protocol has been recommended and legacy has been depreciated. I've just upgraded and can no longer debug my nightmare application. Are there any gotcha's when setting up the JS debugger in vscode launch.json options that one should know about when using the inspector protocol?

If someone could share their working config that would be amazing!

Contributor guide

Research direction
Review the VSCode debugger configuration for Node.js inspector protocol. Check the `type` field in launch.json (should be "node" with `"protocol": "inspector"`) and ensure `runtimeArgs` include ` inspect` or ` inspect brk`. Also examine Nightmare's documentation or examples for debugging setup.
Tech stack
javascript
Domain
testing qa
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Node.jsVSCode
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60