Use case:
Imagine there is the following package.json
:
{
"version": "0.0.1",
"private": true,
"name": "my-app",
"devDependencies": {
"connect-modrewrite": "*",
"csslint": "~0.10.0",
"eslint": "*",
...
}
And eslint
maintainers issued a new package update, which my daily build task has installed via npm install
among other packages. And suddenly the build task fails.
Now, while researching the reasons for a build failure, I want to know if there was a dependency package update that could be a culprit of a daily build failure.
Desired result/output:
eslint 0.15.0 02/15/2015
connect-modrewrite 0.2.0 01/15/2015
...
Basically, I need a list of my project dependencies with a version date. Is it possible to get this kind of meta information with npm
or a third-party tool like npm-check
?
There is a Recently updated packages page which is exactly what I'm looking for, but in the context of my package.json
list of dependencies.
I'm aware about the "avoid surprises" best practices that suggest to list an exact version number for every dependency and upgrade packages cautiously and on-demand.
Aucun commentaire:
Enregistrer un commentaire