Added --save-dev to readme #739

Merged
merged 1 commit into from Jan 8, 2017

Projects

None yet

3 participants

@lukasoppermann
Contributor

I think it would make sense to add the --save-dev flag, since this would mean standard is installed when people clone and npm install a project. Since one advantage is that teams have a common base, this seems to be a typical use case.

@lukasoppermann lukasoppermann Added --save-dev to readme
I think it would make sense to add the `--save-dev` flag, since this would mean `standard` is installed when people clone and `npm install` a project. Since one advantage is that teams have a common base, this seems to be a typical use case.
a58296f
@LinusU
Collaborator
LinusU commented Jan 7, 2017

The build is failing because of sebdeckers/express-history-api-fallback#8

@LinusU
Collaborator
LinusU commented Jan 7, 2017

Also, very small nit, but I personally prefer --save-dev standard (the flag before), and this is what I've seen in most other projects...

@feross
Owner
feross commented Jan 8, 2017

We already cover --save-dev and --global a few paragraphs later in the readme here, but this is the second time someone's opened a PR like this, so okay, sure 🚢

@feross feross closed this Jan 8, 2017
@feross feross reopened this Jan 8, 2017
@feross feross merged commit 3b433fc into feross:master Jan 8, 2017

1 of 2 checks passed

continuous-integration/travis-ci/pr The Travis CI build is in progress
Details
Node Security No known vulnerabilities found
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment