You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> storage-engine@3.0.7 postinstall /usr/lib/node_modules/signalk-server/node_modules/storage-engine
> node ./compatibility/detect.js
fs.js:646
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
Error: EACCES: permission denied, open '/usr/lib/node_modules/signalk-server/node_modules/storage-engine/lib/compatibility/index.js'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.writeFileSync (fs.js:1299:33)
at /usr/lib/node_modules/signalk-server/node_modules/storage-engine/lib/compatibility/detect.js:35:15
at Object.<anonymous> (/usr/lib/node_modules/signalk-server/node_modules/storage-engine/lib/compatibility/detect.js:45:3)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
Steps to reproduce: sudo npm install -g primus or for real add primus as a dependency and install your module with -g.
Filing the issue here for advice as to what to do about it, even if I understand that this is more a diagnostics / storage-engine issue. It seems that diagnostics is a "hard" dependency here, not something that you could just leave as optional.
The text was updated successfully, but these errors were encountered:
I wanted to bring this to your attention and get your feedback - this is not a showstopper, but something to be aware of. Maybe a better way to deal with it would be somewhere upstream.
Version:
^7.3.3
Environment:
Expected result:
--unsafe-perm not needed
Actual result:
Global install with -g fails with
Steps to reproduce:
sudo npm install -g primus
or for real add primus as a dependency and install your module with-g
.Filing the issue here for advice as to what to do about it, even if I understand that this is more a diagnostics / storage-engine issue. It seems that diagnostics is a "hard" dependency here, not something that you could just leave as optional.
The text was updated successfully, but these errors were encountered: