This node causes Node.JS module get-installed-path to stop working

[TotallyInformation]

get-installed-path is used by node-red-contrib-uibuilder to find the install paths for front-end libraries that have been installed using npm.

If this node is installed, the sync version of the function getInstalledPathSync stops working. I've not tried the other version which returns a promise.

The issue lies at line 130 of that module:

const modulePath = filePaths.find((filePath) => {
...

The find function is never executed.

If node-red-contrib-opcua is removed, the function starts working again.

To me, this implies that something that this node is doing is overwriting the native Array.prototype.find function? Everything else appears to be working as normal.

[mikakaraila]

There is actually no exports and Array is not used so it could be overwrite it. I suppose it could come from some underlying dependency instead of directly node-red-contrib-opcua. Have to investigate more...
My first guess is collections package.
montagejs/collections#215

[TotallyInformation]

Hi, thanks for the response. I don't actually use your node myself as I don't have the hardware but as you can see from the reference, one of the users of uibuilder reported it.

extends core types (e.g extends Array.prototype with additional non-enumerable properties like .set)

Urgh! Not a good approach! Sounds like you are right. This illustrates exactly why extending the prototype of a native object isn't a good approach. Too easy to break something.

[TotallyInformation]

Though, I can see that the collections package is actually at v5, you are using v3. Possibly this has been fixed in a later release?

[mikakaraila]

Can you test it now? I am at work and I will have time perhaps later today?

[mikakaraila]

OK, I updated collections and node-opcua to latest ones.

[mikakaraila]

Has anybody tested new version? New one will use JS Map instead of Set, should be better now.