Dissociate NPM release from Binaries releases
So duniter module can be released separately on will, without requiring to make an official release.
So duniter module can be released separately on will, without requiring to make an official release.
Today I can see an annoying consequence of NPM release through Travis: duniter show on NPM some dependencies (not just devDependencies) to other duniter modules.
This is not what is coded into Duniter, but is a side effect of Travis build: we add duniter modules to the final binary using npm install --save
, and as the NPM process occurs in the end of the process, the NPM package saves this modules as dependencies.
Fixed by #952 (closed).