Home
IDEs Support (IntelliJ Platform) | JetBrains
Contact Support
Community
Sign in

Berkqq

Avatar
  • Total activity 24
  • Last activity June 25, 2018 12:33
  • Member since February 12, 2018 16:40
  • Following 0 users
  • Followed by 0 users
  • Votes 0
  • Subscriptions 5
Activity overview Posts (5) Comments (14)
Sort by recent activity Recent activity Votes
  • Created May 03, 2018 20:06
    SOLVED:  This is a problem in version 66 of Chrome.  When using the javascript debugger (from Webstorm in this case) the gapi signIn() call closes the popup too fast.  This results in the signIn() ...
    1. Community
    2. WebStorm
    3. In Webstorm 2018.1.2, I canno longer debug in Chrome
    • 1 vote
  • Created June 25, 2018 12:33
    I'm still getting connection refused.  I just want to confirm that there is nothing my host needs to do or I need to configure on my host other than starting node with those debug port properties. ...
    1. Community
    2. WebStorm
    3. Attach to remote node app
    • 0 votes
  • Created June 24, 2018 20:22
    It's Node 8.11 so I've selected Chrome or Nodejs > 6.3 instead of Node.js < 8.  In Webstorm I've put in my app's IP on the production host and the port as 9229.  On my host I'm setting this option ...
    1. Community
    2. WebStorm
    3. Attach to remote node app
    • 0 votes
  • Created June 24, 2018 15:57
    This is still not working.  I'm using node express and in my package.json I have the line:  "main": "app.js --inspect=0.0.0.0:5858",Then in Webstorm, in my Node.js.Chrome config I have the host set...
    1. Community
    2. WebStorm
    3. Attach to remote node app
    • 0 votes
  • Next ›
  • Last »
Copyright © 2000– JetBrains s.r.o.