PProPanel shows a non-working and misleading way to enable Node.js

PProPanel is misleading. It contains the --enable-nodejs directive in the manifest but that directive does nothing, because:

1. CEFCommandLine is in the wrong place. It’s under <DispatchInfo> instead of under <Resources>.
2. <ExtensionManifest Version="4.0">, instead of “5.0” or higher (but not “8.0” because then your extension is not loaded, of course…).

If we copy the sample to create our own panel, we expect Node.js to work since --enable-nodejs is defined. However, it doesn’t work. This can be verified by debugging in Chrome (cep_node is undefined) and also by enabling verbose logging, opening ~/Library/Logs/CSXS/CEP8-PPRO.log and seeing that CEFCommandLine is not displayed for PProPanel.

Please add documentation of minimum Version and CEFCommandLine location in manifest. I just wasted a whole day on this. The sample here is correct.

Related: #74

Topic

This is an issue regarding:

• The samples contained within this repo.

Versions

• CEP version(s) used [must be 8.x+ for this repo]: 8.0
• Supported CC app(s) and version(s): PPro 12.0

[bbb999]

Apparently, only in my mind. 😉 Pushing, again…

[matangover]

https://github.com/Adobe-CEP/Samples/blob/master/TypeScript/PProPanel-vscode/CSXS/manifest.xml