I can't specify any npm flag

Hi! If I use this package with my project I has a problem. My package.json has a "git dependency" like this:

{
  "peerDependencies": {
    "package": "git+ssh://[email protected]/team/project.git"
  }
}

And npm-install-peers breaks.

I published the v1.1.1 on Windows so end-of-file character is \r\n.
It cause an error on the first line because node is interpreted as node\r.

I'll publish a new version v1.1.2 on Unix system to correct it.

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.

Does not work? I get this syntax error when executing npm-install-peers

$ npm-install-peers

C:\Program Files\nodejs\node_modules\npm-install-peers\index.js:4
const chalk = require('chalk')
^^^^^
SyntaxError: Use of const in strict mode.
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:906:3

Our team and I have started getting the following error when we run npm-install-peers

/Users/kheyalimitra/code/pfm/node_modules/npm/lib/npm.js:130
      throw new TypeError('must call as: npm.load(callback)')
      ^
TypeError: must call as: npm.load(callback)
    at Object.load (/Users/kheyalimitra/code/pfm/node_modules/npm/lib/npm.js:130:13)
    at /Users/kheyalimitra/code/pfm/node_modules/npm-install-peers/dist/index.js:40:9
    at /Users/kheyalimitra/code/pfm/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:123:16
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)

Our team uses npm version 6.14.1 not 7.x.x. We suspect that could be the issue hence added a fix.

Let me know what you all think.
Thanks.

PR link:

#29

I am using virtual machine on windows, and I can't have symlinks. I always install deps with --no-bin-links flag. Could you please add this option to npm-install-peers?

It would also be cool to allow passing other options which are used with npm install.

$ npm i
npm WARN @angular/[email protected] requires a peer of zone.js@^0.7.2 but none was installed.
npm WARN [email protected] requires a peer of @angular/[email protected] but none was installed.
npm WARN [email protected] requires a peer of @angular/[email protected] but none was installed.
npm WARN [email protected] requires a peer of @angular/[email protected] but none was installed.
npm WARN [email protected] requires a peer of @angular/[email protected] but none was installed.
npm WARN [email protected] requires a peer of @angular/[email protected] but none was installed.
npm WARN [email protected] requires a peer of @angular/[email protected] but none was installed.
npm WARN [email protected] requires a peer of @angular/[email protected] but none was installed.
npm WARN [email protected] requires a peer of @angular/[email protected] but none was installed.
npm WARN [email protected] requires a peer of @angular/[email protected] but none was installed.
npm WARN [email protected] requires a peer of [email protected] but none was installed.
npm WARN [email protected] requires a peer of [email protected] but none was installed.

$ npm-install-peers
This package doesn't seem to have any peerDependencies

😢

I was very surprised to see npm-install-peers modifying my files (package.json and npm-shrinkwrap.json) and leaving my Git working tree in a dirty state. Could the implementation of #4 be changed to allow not to modify any files?

currently if i try to use npm-install-peers in an npm script, it fails because it's attempting to require npm but npm is not listed in your deps. setting it in your dependencies will fix this problem...

This is a great tool!
The next step is to write the updated versions back to the package.json where the primary use-case is "Blast! I need to update all of the peer deps and get my npm install working again.."

It would be useful if there was an option to list the declared peer dependencies (in a machine readable format like JSON) without actually installing them. This is similar to my npm feature request to extend npm list to support --only=peer, but even if implemented that would only work for already installed peer dependencies.

currently the CLI doesn't provide a meaning error message. When I run it over a project with 6 peer dependency warnings it says: "This package doesn't seem to have any peerDependencies". This makes no sense and hence it is better you add some examples of successful and failed operation in the main guideline.

I saw it is added in #17

"dependencies": {
  "npm": "< 7.0"
}

This will affect package-lock.json extends for around 3K lines
I understand that with NPM 7, this package will no longer needed

The ES6 features const and class prohibit this from being run on older version of Node.

This is making it hard to test this package on Travis for multiple versions of Node: https://travis-ci.org/eslint/typescript-eslint-parser/builds/161519098