Learn how to use Chrome Developer Tools, a set of web authoring and debugging tools built into Google Chrome, to debug and control Node.js code execution.
- [Instructor] Another client that works with nodes…inspector agent is Chrome Developer Tools…built-in inspector.…The steps for using Chrome DevTools…are very similar to node inspect.…First, make sure that you stop web in PM2.…Then we'll try two different techniques.…The first is to start web with the flag inspect-brk,…which pauses execution on the very first line.…The second is just inspect without pausing execution.…Let's jump right in and switch to VSCode.…
Open up the terminal,…and then we'll turn off the web server.…Type pm2 stop web.…The web status is now stopped.…We're ready to start the web server with…the inspector agent, to type node space --inspect-brk…to break on the first line, and then the path of the script,…servers/web/index, and press return.…The debugger is listening but nobody's attached.…
Let's change that.…Open up Chrome.…We're gonna navigate to a special page.…Type chrome://inspect and press return.…Under remote target, you should see an entry…that matches the debugger process that we just started,…
Author
Released
7/13/2018- Building a troubleshooting mindset
- Why measure performance?
- What's a microservice architecture?
- Managing microservices with PM2
- Effective logging strategies
- Debugging Node.js applications
- Benchmarking performance
- Profiling code execution
- Knowing what to optimize
Skill Level Intermediate
Duration
Views
Related Courses
-
Node.js: Testing and Code Quality
with Jon Peck3h 25m Intermediate -
Node.js: Design Patterns
with Alex Banks2h 11m Intermediate -
Node.js: Deploying Applications
with Kirsten Hunter1h 24m Intermediate
-
Introduction
-
What you should know3m 4s
-
Using challenges44s
-
Demo application tour4m 24s
-
1. Build a Troubleshooting Mindset
-
Finding what went wrong5m 11s
-
Why measure performance?3m 12s
-
Documenting problems2m 36s
-
When is a problem resolved?4m 10s
-
-
2. Introducing Microservices
-
3. Effective Logging Strategies
-
Why and what should I log?6m 26s
-
Choosing a logging library5m 40s
-
Request logging with Morgan6m 39s
-
Correlating requests in logs6m 18s
-
-
4. Debugging Node.js Applications
-
Debugging isn't just logging3m 51s
-
-
5. Measuring Performance
-
Benchmarking performance4m 51s
-
Profiling code execution7m 17s
-
-
Conclusion
-
Knowing what to optimize5m 13s
-
Caching fundamentals2m 54s
-
Next steps2m 23s
-
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.
CancelTake notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.
Share this video
Embed this video
Video: Debugging Node in Chrome DevTools