If a dependency can be used, but you would like npm to proceed if it cannot be found or fails to install, then you may put it in the optionalDependencies object.
That conflicts with what we want: reproducible builds + things changing only when we want them to change.
So we need to fix that.
Secondly, npm install --optional is apparently outdated.
So, lets replace that by npm install --omit=dev --omit=optional. Which would require:
[x] add a patch to signalk-server, that changes package.json to make all dependencies non-optional. There was some discussion about the mdns package, but I checked just now and (a) its installed within Venus OS at the moment, and (b) there is this issue: #, and change the rest to be non-optional.
The NPM definition of an optional dependency is:
That conflicts with what we want: reproducible builds + things changing only when we want them to change.
So we need to fix that.
Secondly,
npm install --optional
is apparently outdated.So, lets replace that by
npm install --omit=dev --omit=optional
. Which would require: