console.log not showing in intelli console when debugging from chrome Follow

You need to start a debug session in WebStorm to see console.log statements in debugger console. See https://confluence.jetbrains.com/display/WI/Starting+a+JavaScript+debug+session

I did all of that and i am able to set break points and what not but the console never has anything in it.  I have been debugging with the chrome debugger for some time, i just can't get the console to work.  I tried the remote debug hookup because the "local" debug wouldn't connect to our external resources.  the console did work when i started the server from WS but it won't if i connect to it remotely.

I am running on an apache server locally so i have to attach to the port through the url

> I tried the remote debug hookup because the "local" debug wouldn't connect to our external resources.  the console did work when i started the server from WS but it won't if i connect to it remotely.

What do you mean by connecting remotely? What does your debug configuration look like?

Console logging works for me regardless of the web server application is hosted on

When I say remote, I mean I am running the web site through apache and then I start it in chrome.  It is an angular app and once I am running the site through chrome, I connect to the debugger.  I can set break points and even see call stack but none of the console logs come through.

I have tried start the site through webstorm but it runs on a different port than apache.  I am not sure where to change that.  But even if I configure the Edit Configuration dialog to use apache, and start it that way, they messages don't come through.  IFF I start it using webstorm and the local port, they do come through but the app doesn't work right because it is hosted in apache, not webstorm.

You need editing your run configuration to specify your app URL on Apache - see https://confluence.jetbrains.com/display/WI/Starting+a+JavaScript+debug+session#StartingaJavaScriptdebugsession-Startingadebugsessionwhenusingadifferentwebserver.

Do you have your project located in Apache doc root? Or, did you set up auto-deployment between your local project and Apache? Or? What does your configuration look like?

This is the debug settings.  I am doing everythiung according to the document you sent, that I can tell

console.log should work using such setup. Can you provide a sample project I can use to recreate the issue?

I seem to have the same difficulty with console.log javascript statements not appearing in the console.  I am debugging the javascript of a web page created by php.  Jetbrains is on Windows 7.  Website is running on Apache 2 on the same box.  The browser is Chrome.

I have set up the configuration.  The rest of javascript debugging appears to work fine.

I have a console.log statement that should be activated by an event.  Weirdly the very first time I tried this it worked and the expected console.log message appeared.  After this it stopped working.  I can restart phpStorm/ webstorm and console.log statements do not appear.

Sorry for the delay on my end

The issue coming up with a sample project is that it contains multiple projects that are running along with a Tomcat server so it would be very difficult to give something you could test with.  I am willing to run any debugging code or special traces if you can assist me with verbose debugging to help you along.

if you notice in this view, I clearly just went over a console.log statement and nothing is in the window

also, for whatever reason, when I try and use the Ctrl-F1 on the tooltip, it never works.  I have to actually click the +.

I'm having the same issue, were you able to resolve it?

unfortunately no.  My setup involves a web server that I cannot give because it is a 3rd party software so for me to give enough to debug with, would be very difficult.  At this point, I just need nuggets to try but I have exhausted all of my options it would seem

I've also the same issue. Are there some new news?

Are you sure that your issue is the same? Console logging got broken recently with Chrome API update. If you are using Chrome 54+, please try upgrading to 2016.3 EAP (release is coming soon) - the issue is fixed there

I am having this problem too. It came about suddenly about a month ago. Before that everything worked fine. (I am also using a local web server).

Something Troy said about multiple projects sparked a thought though. The time mine broke was about the same time I split my project into separate application/framework layers, and imported them both as modules.

Does everyone with this problem also have multiple modules?

Oh - just saw the above post. I am using Chrome 54.

In that case - no chance of a patch? I'm not spending the upgrade cost for this alone...

No patches can be expected, sorry:( This is a breaking change, not something that can be easily backported

I have the same issue with Chrome 50 and IntelliJ 2016.3. Should this combination work?
I had the console output working a few weeks (or was it months?) ago. Then I worked on a Java project and when I came back to my angular 2 project the console output had disappeared :-(

Unfortunately Chrome debugging protocol has changed in version 54 (which is stable channel release since October 12), and 2016.3 supports only the latest protocol.

https://youtrack.jetbrains.com/issue/WEB-24182 is fixed in 2016.3.2 - it will support both protocols

I am running WebStorm 2016.3.1 with Canary 57x and it still doesn't work

works fine for me using WebStorm 163.7743 with most recent Canary ( 57.0.2950.0 )

Must be specific to your setup

Upgraded to Chrome 55 and console output is back again :-)

I would upload a screen cast but I don't have that option in the window :(

you can put it on a file server and provide a link... However I'm not actually sure that it would help - as, according to you, the issue is specific to server being used and project configuration. It's unlikely that the screencast helps here

Honestly I am not sure WHY it doesn't work.  That was just a guess.  I am really not doing anything strange, I just can't pack the project up into a nice little ball to give you. 

I am running the portal through Apache Http.

I am going through a proxy to get to the backend but nothing obscure for the front end.  It is just a browser running angular.js code.  Everything works fine in Chrome debugger and honestly everything works find in WebStorm except the console.  Just frustrating.  I have stopped using the WS debugger.

console.log works for me when hosting application on Apache web server... Can you check if the issue is specific to your project? Try creating a new sample app, hosted on same server - does the problem persist?

how about throwing an error instead?

@Zen1986 haven't got what you mean, sorry. Instead of what? 

Sorry, wrong thread. I didn't read the problem carefully
(⊙_◎)