Home
IDEs Support (IntelliJ Platform) | JetBrains
Submit a request
Community
Sign in
Pierre Mineaud
Total activity
11
Last activity
June 11, 2018 07:21
Member since
November 09, 2017 15:54
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
2
Activity overview
Posts (0)
Comments (9)
Pierre Mineaud
commented,
June 11, 2018 07:21
Hello S Hernandez G, I still have that problem too, it's awful and dirty but here is my solution. Maybe it can helps : Like i said I frost my meteor, so I got something like you : global 1.5.2 a...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
1 vote
Pierre Mineaud
commented,
December 18, 2017 10:10
Got the same problem here. ibus-daemon version 1.5.5Ubuntu 14.04.5Pycharm 2016.2.2 I debbuged myself with the "ibus-daemon -r" command I worked a lot on webstorm, I didn't get this.
Community
IntelliJ IDEA Users
[bug] Keyboard get locked in IntelliJ IDEA
0 votes
Pierre Mineaud
commented,
November 14, 2017 14:25
It sound like I'm stucked with my frost meteor version ! The new EAP is working when I don't use the --release argument. The problem is : I can't use this meteor version and need to use the 1.3.3....
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Pierre Mineaud
commented,
November 14, 2017 08:03
I dunno what I have done, but it works for debugging client side ! I reinstalled webstorm 2017.3 and this time it asked me to convert my project. I said yes and after using the debug mode, I can f...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Pierre Mineaud
commented,
November 10, 2017 16:30
I tried before and I just redone the job with an new instance of meteor. My debugger is turning around and the page never show up. What I have done : - meteor create NewHelloWorld- Launching the We...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Pierre Mineaud
commented,
November 10, 2017 15:23
Is there a possible way to continue to debug in webstorm with a quick fix on my version ? I innocently tried to cheat by changing it in the release file (put "METEOR@1.6"), I can now launch my app...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Pierre Mineaud
commented,
November 10, 2017 07:32
I got a frost version so I got "METEOR@1.4.1.1" in the release file. But when I launch my apps (with /usr/local/bin/meteor --release 1.3.3.1 in debug via webstorm), here is the full error message :...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Pierre Mineaud
commented,
November 09, 2017 16:34
Thx for your answer Elena, I tried it, and got the same error message, and still can't force the --inspect instead of --debug-brk :/
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
0 votes
Pierre Mineaud
commented,
November 09, 2017 15:54
Hi. I'm using Webstorm to code in meteor. Even if my meteor version is frozen in release 1.3.3.1 (I launch it with the --release parameter), the core was updated in meteor 1.6 who use node.js 8. S...
Community
WebStorm
`node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead
1 vote