@WebStormIDE the JB Chrome plugin is acting flaky. Any updates coming? Can't debug with @meteorjs now. Connected to port 51274 not 3000.
-
-
Replying to @FutureAaron
@FutureAaron how do you start client-side debugger? You need tell WebStorm debugger that the app is running on localhost:30001 reply 0 retweets 0 likes -
Replying to @WebStormIDE
@FutureAaron you can create JS debug configuration together with server-side one:pic.twitter.com/DXBzvEQ0h4
2 replies 0 retweets 0 likes -
Replying to @WebStormIDE
@WebStormIDE This is what my setup looks like, and then when I press the debug button, the console/debugger windowspic.twitter.com/maSUHQXgDg
1 reply 0 retweets 0 likes -
Replying to @FutureAaron
@WebStormIDE And no new tab in Chrome opens when I press debug. it did in the past. Thought a plugin issue after reading its feedback.1 reply 0 retweets 0 likes -
Replying to @FutureAaron
@FutureAaron port 61605 is a port number used for server-side debug. Try to create a debug configuration again.1 reply 0 retweets 0 likes -
Replying to @WebStormIDE
@FutureAaron uncheck the box “with JavaScript debugger” and create manually a JS debug configuration with URL http://localhost:30001 reply 0 retweets 0 likes
@FutureAaron then first run Meteor configuration to start the app, then hit debug for the JS configuration to start debugging client-side
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.