Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install the npm-check-updates module during provisioning #484

Merged
merged 1 commit into from
Feb 1, 2015
Merged

Install the npm-check-updates module during provisioning #484

merged 1 commit into from
Feb 1, 2015

Conversation

TobiasBg
Copy link
Contributor

See https://www.npmjs.org/package/npm-check-updates
The module is useful to quickly check for updated Grunt modules in a package.json.

Used by @ocean90 as well: https://core.trac.wordpress.org/ticket/27340#comment:16 :-)

…kage/npm-check-updates) during provisioning, which is useful to quickly check for updated Grunt modules in a package.json.

Used by at least one core committer: https://core.trac.wordpress.org/ticket/27340#comment:16
@jeremyfelt
Copy link
Member

Will this modify anything else during provisioning or does it make the module available to whoever wants to run it manually?

@TobiasBg
Copy link
Contributor Author

TobiasBg commented Nov 9, 2014

It will just make npm-check-updates available on the command line -- so that it can be used in folders that have a package.json.
A plain npm-check-updates will check all modules in the package.json for updated versions and print the results to the command line. npm-check-updates -u would update the version numbers in the package.json, taking away that manual step.

@aaronjorbin
Copy link
Contributor

You can also just use npm outdated --depth 0 to find out if any of your modules are outdated and that comes preinstalled with node.

@TobiasBg
Copy link
Contributor Author

TobiasBg commented Nov 9, 2014

Neat, thanks for that, @aaronjorbin! Can that also update my package.json somehow?

@jeremyfelt jeremyfelt added this to the 1.3.0 (Next Release) milestone Dec 16, 2014
@jeremyfelt
Copy link
Member

I used this the other day on another project to update my package.json and it made me very happy. Don't see any downsides to including it yet.

jeremyfelt added a commit that referenced this pull request Feb 1, 2015
Install the `npm-check-updates` module during provisioning
@jeremyfelt jeremyfelt merged commit bad5277 into Varying-Vagrant-Vagrants:master Feb 1, 2015
@TobiasBg TobiasBg deleted the npm-check-updates branch February 1, 2015 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants