Home
IDEs Support (IntelliJ Platform) | JetBrains
Submit a request
Community
Sign in
Alexey Zerkalenkov
Total activity
9
Last activity
November 30, 2017 15:52
Member since
November 30, 2017 11:16
Following
0 users
Followed by
0 users
Votes
3
Subscriptions
1
Activity overview
Posts (0)
Comments (5)
Sort by recent activity
Recent activity
Votes
Created
November 30, 2017 15:52
Great! Thank you!
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Created
November 30, 2017 14:32
Exactly! This is the problem I'm talking about. In the previous version (2017.2) there was a registry flag, which forced WebStorm use an old debug option, now it is gone. Why?! Why you rely only on...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Created
November 30, 2017 13:21
We run Luna which is a custom node interpreter based on Node 7.4.0: This is not system wide registered NodeJS interpreter. Also when I use `nvm` and point system to use Node 7.4.0, it does not help...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Created
November 30, 2017 11:49
There is no inspector support in Node 7.4.0. When I try to debug Luna application in WebStorm 2017.3 I get an error:Inspector support is not available with this Node.js build.../Luna: bad option: -...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Created
November 30, 2017 11:16
After update to WebStorm 2017.3 I have the same problem with Luna / Node 7.4.0:`Luna: bad option: --inspect-brk=50228`I've inspected registry in there is no option js.debugger.node.use.inspect ther...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes