--save is no longer needed

[SamCortopassi]

--save is on by default as of npm 5. npm install create-subscription is equivalent to npm install --save create-subscription now

[facebook-github-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[raunofreiberg]

Not everyone has/or is using NPM v5. Might be safer to keep it around?

[SamCortopassi]

npm 5 came out a year and a half ago, so it would only effect npm <=4. How far back does React support npm versions?

https://blog.npmjs.org/post/161081169345/v500

[hg-pyun]

I think it's good to note explicitly because there may still be users using previous versions of NPM.

[devrchancay]

And what do you think about leaving it like that?

npm install create-subscription --save

--save option for versions less than npm 5

[JoeCortopassi]

This pr just maintains consistency in this project, and most other major projects using npm. A year and a half is an eternity in js frameworks, especially something that only lives client-side

#13756

[devrchancay]

That said, I think you should close this PR @SamCortopassi

[JoeCortopassi]

@devrchancay why? It's a good pr, it updates the docs

[JoeCortopassi]

@gaearon good to merge for consistency?

[JoeCortopassi]

???

[threepointone]

Looks good to me, merging. Thanks @JoeCortopassi!