OPCUA Issues

[danielpeintner]

We seem to run into issues of OPCUA versioning.
see for example https://github.com/eclipse/thingweb.node-wot/pull/394/checks?check_run_id=2038479109

Error: node_modules/node-opcua-basic-types/dist/attributeIds.d.ts(34,33): error TS2694: Namespace '"fs"' has no exported member 'OpenMode'.

I assume this has to do with recent opcua updates and us having no "fixed" version in package.json.

Does anyone mind if I update to "fixed" versions e.g.,

• "node-opcua": "^2.4.3" --> "node-opcua": "2.4.3"
• "node-opcua-client": "^2.1.8" --> "node-opcua-client": "2.1.8"

@relu91 @egekorkan or do you think it is caused by other aspects?

[danielpeintner]

related to #379

[danielpeintner]

OR like @relu91 pointed out include package-lock.

Question. What do you prefer?

• fix version OR
• add package-lock

[egekorkan]

I see it happening in other projects and that's why I like pushing lock files :)

[relu91]

I'll add package-lock too. As another compelling evidence towards this decision, there's also the fact that neither .gitignore.io suggests ignoring package-lock.json files.

[mjkoster]

I just ran into the same issue trying to build. I can wait until the issue is resolved, or if it will be a while I could work around, since I don't use OPC UA at the moment