Debugging Node: Remove References to Debugging with Chrome #30415
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The Lesson overview as well as the Assignment sections have been updated such that all references related to debugging with Chrome are removed.
mao-sz
requested changes
Nov 14, 2025
| ### Introduction | ||
|
|
||
| Up until this point, you've likely only relied on the browser's DevTools to debug your code. <span id="two-ways">When it comes to debugging Node and server side code, VS Code has a handy built-in debugger that you can use to debug directly in your editor! Additionally, you can also set Google Chrome up to debug Node and get the full benefits of the Chrome DevTools. </span> Ultimately, this lesson will familiarize you with the Node debugger, which is a critical tool at this point in your learning, and will likely be a key tool you use daily in your professional life. | ||
| Up until this point, you've likely only relied on the browser's DevTools to debug your code.<span id="two-ways"> When it comes to debugging Node and server side code, VS Code has a handy built-in debugger that you can use to debug directly in your editor! Additionally, you can also set Google Chrome up to debug Node and get the full benefits of the Chrome DevTools, but this is beyond the scope of this lesson. </span> Ultimately, this lesson will familiarize you with the VS Code Node debugger, which is a critical tool at this point in your learning, and will likely be a key tool you use daily in your professional life. |
Contributor
There was a problem hiding this comment.
Needed to actually remove all references to using the Chrome debugger for Node purposes.
But while we're at it, also tweaked the overall wording to better flow with the rest of the curriculum since people may have used the VSC debugger already at parts.
Suggested change
| Up until this point, you've likely only relied on the browser's DevTools to debug your code.<span id="two-ways"> When it comes to debugging Node and server side code, VS Code has a handy built-in debugger that you can use to debug directly in your editor! Additionally, you can also set Google Chrome up to debug Node and get the full benefits of the Chrome DevTools, but this is beyond the scope of this lesson. </span> Ultimately, this lesson will familiarize you with the VS Code Node debugger, which is a critical tool at this point in your learning, and will likely be a key tool you use daily in your professional life. | |
| Up until this point, you've may have only relied on the browser's DevTools to debug your code. When it comes to debugging Node and server side code, VS Code has a handy built-in debugger that you can use to debug directly in your editor! Hopefully you'll have also made use of this at some points earlier in the curriculum already, but ultimately, this lesson will familiarize you with the VS Code Node debugger, which is a critical tool at this point in your learning, and will likely be a key tool you use daily in your professional life. |
Contributor
Author
There was a problem hiding this comment.
Sounds good, my latest commit uses your suggested wording.
|
|
||
| The following questions are an opportunity to reflect on key topics in this lesson. If you can't answer a question, click on it to review the material, but keep in mind you are not expected to memorize or master this knowledge. | ||
|
|
||
| - [What are two ways to debug Node?](#two-ways) |
Contributor
There was a problem hiding this comment.
The knowledge check question (both wording and link) needs changing due to the removal of Chrome/Node debugging in the intro
- [What can you use to debug Node?](#introduction)
Contributor
Author
There was a problem hiding this comment.
Updated in the latest commits as well.
mao-sz
approved these changes
Nov 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Lesson overview as well as the Assignment
sections have been updated such that all
references related to debugging with Chrome
are removed.
Because
This PR is submitted in order to update the 'Debugging Node' lesson from the NodeJS Course. The issue number is provided below.
This PR
Issue
Closes #29444
Additional Information
Pull Request Requirements
location of change: brief description of changeformat, e.g.Intro to HTML and CSS lesson: Fix link textBecausesection summarizes the reason for this PRThis PRsection has a bullet point list describing the changes in this PRIssuesection