You will see the debugger listening to port XXX (*NB: javascript debugger bundle is in IDE workspace )Įaxample: node -debug-brk my-helloworls-app.js (you can start with Eclipse for Committers -> simple to start)
install Javascript Development Tools Chromium V8 remote debugger tests from that p2 repo install into latest eclipse using local update site from site/target/repository inside local git repoĬreate a local p2 repo declared wtp-parent/pom.xml - easy to use.build via "mvn clean install -Pbuild-individual-bundles".The latest and greatest release, as ofi March 2016, s v 1.1 (Chrome 31) You can search developer.chrome > chrome debugger-protocol to see specs so it supports WIP (webkit inspection protocol). Firefox (as IE) is potentially debuggable via adapter, plus some implementations are already available on Ĭhromium was forked from Webkit.IE is potentially debuggable via "IE Diagnostics Adapter".Safari is debuggable trough bridge developed by Google,.All browsers based on Chromium can debug JS in the same way as Chromium does (* i.e.It actually works with most of the latest browsers: Google changed license to EPL and this made the Eclipse CQ much faster, because the license was changed by source owner and released into original repository.Īfter CQ was done, the code was refactored to .chromium namespace and released to the JSDT git repository. This Confcall is about Debugger : how it was contributed, how it works + info on current development status (at Neon M6)Ĭhrome dev tools was developed by Google and was released under Eclipse EPL Participants: Dennis, Chuck, Max, Gorkem, Victor, Alexey, Adalberto Ilya, Orlando, Patrik, Mathieu