Check Editor Compatibility

[sammachin]

Test for compatibility with the Monaco editor

[Steve-Mcl]

The issue was an old (but well used) node-red contrib node was duplicated (and modified) by several users to create new nodes. The original contrib node had a copy of multiple-select.js (V1.4.2) embeded in its src (rather than required

While it might prove difficult to test for this embeded js file & its version, we can certainly check for installs of the below nodes where version is < the version of the known fix for these items?

• node-red-contrib-deconz-test-zehir - issue raised - fixed in v1.3.3
• node-red-contrib-defaro - issue raised
• node-red-contrib-zigbee2mqtt - issue raised - fixed in v0.6.9
• node-red-contrib-wirenboard - issue raised - fixed in v3.5.1
• node-red-contrib-deconz - Issue raised - fixed in v1.3.3
• node-red-contrib-zway - Issue raised - fixed in v1.0.0
• node-red-contrib-spruthub - Issue raised - fixed in v1.0.4

[sammachin]

So if we were checking a new node outside of a Node-RED install we would need to look for that multiple-select.js file in the static folder?

What about if the node is fetching it externally, can it come from npm? or is it a CDN thing?

[Steve-Mcl]

What about if the node is fetching it externally, can it come from npm? or is it a CDN thing?

If we can check the version is > 1.4.2 then it is ok (as we can with a NPM and sometimes a CDN if it is encoded in the name or meta data is available).

If we find a file in a static folder named multiple-select.js then perhaps a warning unless we know the package to by updated (as above)?

In fact, static files are prone to falling behind the original repo/package (assuming they are a copy of an actual package as this one is) - hmmmm - can-o-worms