when toggling a breakpoint, get .js.chromium' does not exist". was: Question about the Chrome dev tool in Nodeclipse

[RaymondQiu]

Hey guys, I have a question about the Chrome dev tool in Nodeclipse. I saw a change that make the org.chromium.debug.ui.editors.JsEditor to extend the ComilationUnitEditor (JSDT JS editor). In my nodeclipse, I also installed JSDT plug-ins which included the org.eclipse.wst.jsdt.debug.ui plug-in.

When I tried to toggle a breakpoint in a virtual js file created by the chrome tools, I got an error saying "Resource '/ /C__DemoWorkspaces_Demo31_FirstApp_node_modules_express_lib_express.js.chromium' does not exist".

I investigated a little bit. The error was caused by org.eclipse.wst.jsdt.debug.internal.ui.breakpoints.ToggleBreakpointAdapter was used to toggled breakpoint instead of org.chromium.debug.core.model.LineBreakpointAdapter$ForVirtualProject and org.eclipse.wst.jsdt.debug.internal.ui.breakpoints.ToggleBreakpointAdapter could not recognized the virtual file. So that meant I can not have both nodeclipse and full JSDT together, right? Thanks.

[paulvi]

The breakpoint sync-ing was contributed by @tomotaro1065 , but he is silent for about a year, I cannot comment more then it is seen from the code.

But Nodeclipse is great together with full JSDT, so if at some point you see errors, that is bug.

Bugs should be raised with enough info about environment and how to reproduce .

Code changes are welcomed.

[ghost]

JSDT is not that great in my opinion as it's still hooked into ES3 when ES6 is now out there. Unfortunetely it's not optional — you can't remove ES3 JSDT as a plain package from your Eclipse installation. It's deeply bounded within Nodeclipse as far as I understand it therefore I don't see how it could provide a different path for any IDE task - debugging included. A typical problem is erroneous syntax checking like this one below:

This is wrong even for ES3: if 'default' was a key word even as data key within a json object then it should be colorized as such instead of raising a buggeous syntax error that will pollute my MEAN projects for ever...

[paulvi]

@nodeleaf Hi Patrick, this is not related to ES5 or ES6 support. Please create new issue if you want to collaborate on that.

[ghost]

@paulvi My point was: I don't see how JSDT could be used instead of Nodeclipse's - when you are using Nodeclipse IDE. If it was installed as a 'stand alone' plugin then this is not Nodeclipse but JSDT issue. Now about ES3 in JSDT: this is old story I re-instantiated above to expose one serious limit of JSDT among many others. As far as I understand it, ES5 support in JSDT 3.6 was deferred therefore I am afraid there is not much to collaborate about this topic — beside getting rid of JSDT in Nodeclipse but this is hardly an option don't you think?

[paulvi]

very old discussion.

maybe should be close as is (especially if quiet)

[dPhantum]

This is still an issue in Eclipse, I am using the Eclipse PDT and it is never ending popping up.

[dPhantum]

So it looks like the fix is to remove the NodeEclipse plugin. If I don't hear back I suppose there is no resolution.

[paulvi]

"never ending popping up" is new issue.

@dPhantum Can you put screenshot and some entries in Error Log

as new issue

[dPhantum]

New issue created, see https://github.com/Nodeclipse/nodeclipse-1/issues/224