Lines Matching +full:fetch +full:- +full:depth

1 .TH "NPM\-OUTDATED" "1" "January 2022" "" ""
3 \fBnpm-outdated\fR \- Check for outdated packages
21 you're running \fBnpm outdated \-\-global\fP, or the package isn't included in
22 \fBpackage\.json\fP), then \fBwanted\fP shows the currently\-installed version\.
26 with a dist\-tag of \fBlatest\fP\|\. This may or may not be the maximum version of
27 the package, or the most\-recently published version of the package, depending
28 on how the package's developer manages the latest dist\-tag \fInpm\-dist\-tag\fR\|\.
31 \fBnpm outdated\fP defaults to a depth of 0, so unless you override that, you'll
32 always be seeing only top\-level dependencies that are outdated\.
34 \fBpackage type\fP (when using \fB\-\-long\fP / \fB\-l\fP) tells you whether this package is
38 \fBhomepage\fP (when using \fB\-\-long\fP / \fB\-l\fP) is the \fBhomepage\fP value contained in the…
51 glob          5\.0\.15   5\.0\.15    6\.0\.1  test\-outdated\-output
52 nothingness    0\.0\.3      git      git  test\-outdated\-output
53 npm            3\.5\.1    3\.5\.2    3\.5\.1  test\-outdated\-output
54 local\-dev      0\.0\.3   linked   linked  test\-outdated\-output
55 once           1\.3\.2    1\.3\.3    1\.3\.3  test\-outdated\-output
81 \fBnpm update\fP have to fetch Git repos to check\. This is why currently doing a
85 uses dist\-tags to manage its \fBlatest\fP and \fBnext\fP release channels\. \fBnpm update\fP
135 .SS depth
144 Max depth for checking dependency tree\.
150 npm help dist\-tag