segment-boneyard/nightmare

vscode debugging nightmare - launch.json

Open

#1341 opened on Dec 12, 2017

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

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

Tech stack
typescript
Domain
developer experience
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
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.
clear
Prerequisites
VSCodeNode.js 8+nightmare
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue requests a working VSCode launch.json configuration for debugging a Nightmare.js application with the Node.js inspector protocol. The repository is archived and the issue is old, so it's unlikely to receive a direct response. Contributors should look for examples in the VSCode documentation or in active projects using Nightmare.js to derive a working config. The existing comments (if any) might contain user attempts, but they are not provided here.