microsoft/vscode-recipes

Add recipe for debugging Node in Vagrant

Open

#67 opened on Jan 28, 2018

View on GitHub
 (0 comments) (2 reactions) (0 assignees)JavaScript (5,672 stars) (600 forks)batch import
enhancementhelp wanted

Description

https://stackoverflow.com/questions/30120477/debugging-a-node-app-hosted-on-a-vm-using-visual-studio-code

http://neilk.net/blog/2013/08/21/how-to-debug-node-dot-js-from-within-vagrant/

Contributor guide

Tech stack
nodejs
Domain
documentation
Issue type
documentation
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.
clear
Prerequisites
Basic Node.js knowledgeFamiliarity with VagrantVS Code debugging basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Review the provided StackOverflow and blog post links to understand the common steps for debugging Node.js inside a Vagrant VM. Then create a new recipe in the vscode recipes repository (e.g., add a folder named 'node vagrant' with a README.md) following the existing recipe format. Include instructions for setting up remote debugging in Vagrant and configuring VS Code's launch.json to attach to the Node process.