JavaScript debugging

Is js debugging enabled in pycharm 2.0 EAP?

I see it in the help docs, but I don't see it enabled anywhere within the IDE (plugins, or the project settings dialog).

Any direction would be appreciated!

5 comments

Hello Christian,

The JavaScript debugger will be included in the next PyCharm 2.0 EAP. The

documentation describing its availability in the current version is erroneous.

Is js debugging enabled in pycharm 2.0 EAP?

I see it in the help docs, but I don't see it enabled anywhere within

the IDE (plugins, or the project settings dialog).

Any direction would be appreciated!

--

Dmitry Jemerov

Development Lead

JetBrains, Inc.

http://www.jetbrains.com/

"Develop with Pleasure!"

0

Javascript debugging is enabled in the current beta version, right? I see it in the settings and debug configuration as well.

I just can't figure out how it actually works though. If I run the Django server in debug mode, the browser is automatically opened, and according to the config it should be debugging javascript, but setting breakpoints doesn't do anything.

Is there any documentation available on how to use this feature? Thanks!

0

I am facing the same problem.

Debugging a html page directly from PyCharm works. Then it stops at the breakpoints.

But when I debug the django server and run a dynamic html page - with javascript - from a django template html, then I can not break into this.

Any clues? Am I doing something wrong or is this feature not yet supported, or a bug?

Thanks, Patrick

0
I'm currently evaluating PyCharm for our company, and this problem is a significant disappointment in an otherwise impressive IDE. Here's what I'm doing:

+  I put a breakpoint in file <project root>/static/scripts/core/selector.js
(I already know that the breakpoint should be hit by previously testing using a breakpoint in Chrome.)

+  I configure a remote JavaScript Debug configuration to open URL http://localhost:8000/ and to map the above file to URL http://127.0.0.1:8000/site_media/static/scripts/core/selector.js?cacheb=2, which is what I see in Django's log of GET requests. I've also tried URLs without the "http://127.0.0.1:8000" part and without "?cacheb=2" (in both this configuration and the request so that they match).

+  After starting my app by running my Django server debug configuration, I then run my JavaScript Debug configuration. I see both tabs in the Debug frame, both showing they are running. Chrome automatically opens a new tab for http://localhost:8000/ just fine.

+  I interact with my app and click the element I know should hit the breakpoint. Nothing happens in PyCharm.

In Firefox, it's even worse! A window for URL http://localhost:8000/ opens, but then the PyCharm debugger opens file jquery-1.7.1.min.js, which I've never touched. Furthermore, PyCharm slows to a crawl, where you click a button and have to wait a minute or two to see anything happen. I keep clicking the green arrow, then after a minute or two, the UI finally reacts, eventually stopping once again in jquery-1.7.1.min.js. It never stops at my breakpoint in selector.js.

I'm running all the latest versions of Mountain Lion, Chrome, Firefox, and PyCharm.

I haven't tried debugging JavaScript by openning an HTML file directly, because with Django, you never really have non-template HTML files or URLs to them.

Will this be fixed soon? Thanks.
0

Please sign in to leave a comment.