Open danielpeintner opened 3 weeks ago
The change in package-lock.json that seems to cause issues is the following
Not sure what we can do here!?
See attached the package-lock.json
file that gets generated. I noticed that there are varying versions for @types/readable-stream
:
Could it be that there is a change between v2 and v4 that causes the issue/inconsistency?
node-wot itself (package.json wise) has it in root only (and twice as indirect dependency in COAP v2 and MQTT v4)
node-wot itself (package.json wise) has it in root only (and twice as indirect dependency in COAP v2 and MQTT v4)
FYI: updating it to "^4.0.5" doesn't help. I think the issue is that CoAP still uses v2, see
https://github.com/coapjs/node-coap/blob/0ac5017e605b7ab06a703a9b28a5f582b3217b93/package.json#L58
@JKRhb do you know whether there is any plan to upgrade?
EDIT: @types/readable-stream
in node-coap are v2 but readable-stream
is v4. Could this be an issue?
https://github.com/coapjs/node-coap/blob/0ac5017e605b7ab06a703a9b28a5f582b3217b93/package.json#L64C6-L64C21
I've just published a new version of node-coap
with updated dependencies :) I hope that will contribute to resolving this issue.
@JKRhb I updated the coap library but I still run into issues, see https://github.com/eclipse-thingweb/node-wot/pull/1297
Hmm, that is very strange :/ But this seems to also occur with other bindings, if I am not mistaken, as the error persists even after removing the CoAP binding from the workspace.
True. I didn't try it before.
It fails for me if I try to use td-tools
only.
What I also noticed is that we refer to readable stream in td-tools ts.config.json
file
Does anyone know why we need it? Removing it causes issues with importing debug
and ajv-formats
...
While working on https://github.com/eclipse-thingweb/node-wot/pull/1291 I tried to update all dependencies. Essentially I did the following:
package-lock.json
filenode_modules
folders etc.)npm install
npm dedupe
(see https://github.com/eclipse-thingweb/node-wot/pull/765#issuecomment-1133772886)like mentioned in our README under "Development Internals"
So far so good, no issue. Anyhow, afterwards
npm run build
does not work and fails since some time. See below the error