Enabling Node.js in PProPanel sample crashes the debugger about samples HOT 9 CLOSED

The problem is in CEP.

You may be right. This problem report is specific to PProPanel.

No PPro panel developer has reported problems debugging Node.js.

If the problem is reproducible in CEP HTML Test Panel, we can have the CEP team investigate further.

from samples.

Just turning on Node.js is unlikely to succeed; your result is, unfortunately, unsurprising.

Can you get CEP HTML Test Panel 1 to successfully detect whether Node.js is enabled?

from samples.

@bbb999 with the current manifest.xml Node.js is not enabled, if in the console I try to get any Node.js module, window.require and window.cep_node are undefined (in http://localhost:7777)

In the other hand if I change the manifest.xml as I described in my previous comment, I can get any Node.js module without problem because window.require and window.cep_node exist but, enabling this produces the described bug

from samples.

Hello, I have the same issue, can you please share if you've managed to fix it?

from samples.

@venetak I haven't found a solution for Windows yet, if you have a Mac, use it for the debugging.

from samples.

@fcarrilLB Thank you.

from samples.

@bbb999 Do we have any progress on this? Where is the best place to raise the issue, so that Adobe considers it?

from samples.

There has been no progress on adding Node.js usage to PProPanel. Demonstrating Node.js isn't PProPanel's mission, so that's unlikely to change.

I'm told Node.js works, within CEP HTML Test Panel. Has anyone tried that?

from samples.

@bbb999 NodeJS works on any project. The problem with it is, that it breaks the CEP Chrome remote debugging. It is not related exclusively to any sample. The problem is in CEP.

from samples.