Home
IDEs Support (IntelliJ Platform) | JetBrains
Contact Support
Community
Sign in
Alex
Total activity
7
Last activity
January 25, 2018 12:42
Member since
January 24, 2018 19:56
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
0
Activity overview
Posts (0)
Comments (7)
Alex
commented,
January 25, 2018 12:42
OK - I've done that... but it made no difference. The log above suggested there was a build version mismatch... so I re-installed the NodeJs plugin - which has fixed the problem. I now have the run...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Alex
commented,
January 25, 2018 10:29
You want the whole log or is this line enough?? : 2018-01-19 10:41:31,284 [ 1140] INFO - llij.ide.plugins.PluginManager - Plugin 'NodeJS' can't be loaded because: Plugin since-build or until-bu...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Alex
commented,
January 25, 2018 10:15
Note the message on the right about this being based on the default settings
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Alex
commented,
January 25, 2018 10:14
Hi Elena, I've just removed the '~/Library/ApplicationSupport/WebStorm2017.3' folder as requested and and reinstalled a fresh 2017.3 Here's a screenshot of the run config's default options, without...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Alex
commented,
January 24, 2018 22:03
Ok... well I’m on Mac high Sierra & the node.js run config default option not only disappears when I upgrade 2017.2 > 2017.3, but my saved run config becomes invalid. Then when I downgrade again, t...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Alex
commented,
January 24, 2018 21:32
The option I was referring to is the ‘node.js’ default run configuration - you now only have a ‘npm’ Run configuration in 2017.3 It is purely incidental that I was using the ‘nodejs’ run config to ...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Alex
commented,
January 24, 2018 19:56
In 2017.3, the 'node.js' run configuration default setting was removed which broke my debugging capabilities. Now there's only 'npm' as a run config option which doesn't allow me to point an interp...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes