Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

node --inspect appears to be broken or unsupported

See original GitHub issue

See https://github.com/facebook/jest/issues/1652. As of this issue being fixed in Jest and Node 8.4, this should be fixed in create-react-app but I can’t get it to work.

Is this a bug report?

Yes

Can you also reproduce the problem with npm 4.x?

Yes

Which terms did you search for in User Guide?

inspect

Environment

node -v: v8.4.0
npm -v: 4.6.1 and 5.3.0 (confirmed on both versions)
npm ls react-scripts: 1.0.11
Operating system: macOS
Browser and version: Google Chrome Version 60.0.3112.101 (Official Build) (64-bit)

Steps to Reproduce

Open chrome://inspect/#devices in Chromium.
Enable networking and forward localhost:9229.
Set a debugger breakpoint in a test file.
node --inspect-brk node_modules/.bin/react-scripts test
Inspect the target in Chromium.
Resume script execution.
Wait for tests to complete/break.

Expected Behavior

Chromium debugger stops on debugger breakpoint.

Actual Behavior

Chromium debugger doesn’t stop on breakpoint and remains at the beginning of the script.

Issue Analytics

State:
Created 6 years ago
Comments:12 (10 by maintainers)

Top GitHub Comments

5reactions

Timercommented, Aug 17, 2017

Sorry @nickmccurdy, this should do it:

./node_modules/.bin/react-scripts --inspect-brk test --env=jsdom --runInBand

2reactions

gaearoncommented, Aug 18, 2017

We need to add a more ergonomic way of running it that doesn’t require specifying --runInBand manually and then document it.

Top Results From Across the Web

debug-brk` are invalid. Please use `node --inspect` or `node

seems the Node.js version babel-node is using doesn't accept `--debug-brk` option, and Webstorm can't detect what Node.js version is being ...

The engine "node" is incompatible with this module

yes , you are getting this error because of incompatibility between the package version and node engine. – Shubham Sharma. Jun 16, 2019...

Debug Node.js Apps using Visual Studio Code

The Visual Studio Code editor includes Node.js debugging support. Set breakpoints, step-in, inspect variables and more.

How to perform an unsupported conversion from a RHEL ...

This document provides instructions on how to perform an unsupported conversion of your operating system from a different Linux distribution ...

Node.js v19.3.0 Documentation

If the browser displays the string Hello, World! , that indicates the server is working. Assert#. Stability: 2 - Stable. Source Code: lib/assert.js....