Installed peers get to package.json in "dependencies" section when using npm 5

[jehy]

Installed peers get to package.json in "dependencies" section when using npm 5. This is likely related to npm 5 adding to "dependencies" even without "save" flag.

This can ve avoided with setting flag npm config set save false cbut setting this for user environment is wrong.

Also seems that we can use --no-save flag, I am gonna test it.

UPD. Looks fine, added a PR.

[jehy]

It is possible that I spelled option wrong, if so - check marapper@07fc6a6

[sschuberth]

Isn't this very related to my issue #12?

[sebastiandedeyne]

1.2.0-rc.1 should fix this. Could anyone give it a spin?

[alexindigo]

It's because of this line: https://github.com/spatie/npm-install-peers/blob/master/src/index.js#L33

There is no no-save option in npm, --no-save argument is translated into save: false option.

[MarkChrisLevy]

@sebastiandedeyne In 1.2.0-rc.1 this is not fixed. As @alexindigo noted, there should be "--no-save" argument, not "no-save".

[alexindigo]

@mmlleevvyy Checkout npmjs.org/install-peers it has that issue fixed and automates things a little bit further :)

[sebastiandedeyne]

Released 1.2.0-rc.2 with a fix for the --no-save argument.

[alexindigo]

I think it works a little bit different from what your fix implies.
--no-save is parsed from cli args into options['save'] = false.

[sebastiandedeyne]

Published another go

[alexindigo]

Looks good 👍

[sebastiandedeyne]

Stable version 1.2.0 has been released