Closed chameleonbr closed 6 years ago
If I change the dependencies all works ok.
"dependencies": {
"nightmare": "^2.10.0",
"nightmare-download-manager": "^0.2.4",
"nightmare-upload": "^0.1.1",
"unfluff": "^3.0.0"
},
Interesting. We'll need further steps to reproduce the issue; OS platform/version?
I'm behind HTTP proxy, git:// not working with HTTP proxy. It is also common practice for the dependencies to be bound by the npm itself and versioned. So if someone changes the working of a library does not break your package. Look at NodeRED package.json (https://github.com/node-red/node-red/blob/master/package.json) as example.
Ahh, yes I see a few packages that could conflict without a forward compatible identifier ^. Will make the change and test further.
Resolved in 9463b885534358e29ce304c741cf6f568521c26f. New version 1.1.2 pushed. flows.nodered.org should update shortly.
Thanks for fix. It's working now.
I've tried with and without --unsafe-perm option and received same error.