Debugging Node.js Applications in WebStorm Using Chrome DevTools
Learn how to configure WebStorm to debug Node.js apps using Chrome DevTools, set breakpoints, and use Live Edit.
Loading…
ReadMeFeed / Community knowledge
#chrome-devtools
Real questions. Useful conversations. Find the people who know your stack.
nodejs
webstormTesting Responsive Pages with Chrome DevTools Device Mode: Viewports, Throttling, and Touch
Use Chrome DevTools Device Mode to emulate mobile viewports, DPR, throttled networks, and touch input — plus the limits of emulation and when you still need real hardware.
chromeDebugging TypeScript in WebStorm: Mapping IDE Breakpoints to Chrome
Learn how to integrate WebStorm's debugger with Chrome to set breakpoints directly in TypeScript source files using source maps and the Chrome DevTools Protocol.
Puppeteer in Docker: pipe transport vs. WebSocket endpoint for avoiding a publicly reachable debugging port
We run Puppeteer inside Docker containers on a shared host, and the current setup launches Chrome with the default WebSocket transport. My concern is the DevTools endpoint: anyone who can reach the debugging port gets full control of the browser, including cookies and page data, with no authentication. The default binding appears to be loopback-only, but con
docker
puppeteer