Linux lorencats.com 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l
Apache/2.4.59 (Raspbian)
: 10.0.0.29 | : 216.73.216.10
Cant Read [ /etc/named.conf ]
7.3.31-1~deb10u7
root
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
npm /
cli /
[ HOME SHELL ]
Name
Size
Permission
Action
npm-access.html
5.5
KB
-rw-r--r--
npm-access.md
2.47
KB
-rw-r--r--
npm-adduser.html
6.23
KB
-rw-r--r--
npm-adduser.md
2.68
KB
-rw-r--r--
npm-bin.html
3.05
KB
-rw-r--r--
npm-bin.md
288
B
-rw-r--r--
npm-bugs.html
3.97
KB
-rw-r--r--
npm-bugs.md
890
B
-rw-r--r--
npm-build.html
3.26
KB
-rw-r--r--
npm-build.md
476
B
-rw-r--r--
npm-bundle.html
2.91
KB
-rw-r--r--
npm-bundle.md
339
B
-rw-r--r--
npm-cache.html
5.78
KB
-rw-r--r--
npm-cache.md
2.56
KB
-rw-r--r--
npm-ci.html
4.6
KB
-rw-r--r--
npm-ci.md
1.66
KB
-rw-r--r--
npm-completion.html
3.5
KB
-rw-r--r--
npm-completion.md
797
B
-rw-r--r--
npm-config.html
4.52
KB
-rw-r--r--
npm-config.md
1.39
KB
-rw-r--r--
npm-dedupe.html
4.08
KB
-rw-r--r--
npm-dedupe.md
1.33
KB
-rw-r--r--
npm-deprecate.html
3.44
KB
-rw-r--r--
npm-deprecate.md
719
B
-rw-r--r--
npm-dist-tag.html
6.19
KB
-rw-r--r--
npm-dist-tag.md
2.71
KB
-rw-r--r--
npm-docs.html
4.04
KB
-rw-r--r--
npm-docs.md
989
B
-rw-r--r--
npm-doctor.html
7.84
KB
-rw-r--r--
npm-doctor.md.gz
2.04
KB
-rw-r--r--
npm-edit.html
3.85
KB
-rw-r--r--
npm-edit.md
850
B
-rw-r--r--
npm-explore.html
3.76
KB
-rw-r--r--
npm-explore.md
869
B
-rw-r--r--
npm-help-search.html
3.51
KB
-rw-r--r--
npm-help-search.md
807
B
-rw-r--r--
npm-help.html
3.87
KB
-rw-r--r--
npm-help.md
816
B
-rw-r--r--
npm-init.html
3.79
KB
-rw-r--r--
npm-init.md
978
B
-rw-r--r--
npm-install-test.html
3.43
KB
-rw-r--r--
npm-install-test.md
705
B
-rw-r--r--
npm-install.html
23.61
KB
-rw-r--r--
npm-install.md.gz
5.23
KB
-rw-r--r--
npm-link.html
5.6
KB
-rw-r--r--
npm-link.md
2.36
KB
-rw-r--r--
npm-logout.html
4.15
KB
-rw-r--r--
npm-logout.md
1.13
KB
-rw-r--r--
npm-ls.html
5.64
KB
-rw-r--r--
npm-ls.md
2.14
KB
-rw-r--r--
npm-outdated.html
6.94
KB
-rw-r--r--
npm-outdated.md
3.34
KB
-rw-r--r--
npm-owner.html
3.87
KB
-rw-r--r--
npm-owner.md
1.08
KB
-rw-r--r--
npm-pack.html
3.47
KB
-rw-r--r--
npm-pack.md
724
B
-rw-r--r--
npm-ping.html
3.09
KB
-rw-r--r--
npm-ping.md
418
B
-rw-r--r--
npm-prefix.html
3.3
KB
-rw-r--r--
npm-prefix.md
460
B
-rw-r--r--
npm-profile.html
5.67
KB
-rw-r--r--
npm-profile.md
2.82
KB
-rw-r--r--
npm-prune.html
4.11
KB
-rw-r--r--
npm-prune.md
1.25
KB
-rw-r--r--
npm-publish.html
6.18
KB
-rw-r--r--
npm-publish.md
2.66
KB
-rw-r--r--
npm-rebuild.html
3.01
KB
-rw-r--r--
npm-rebuild.md
389
B
-rw-r--r--
npm-repo.html
3.41
KB
-rw-r--r--
npm-repo.md
662
B
-rw-r--r--
npm-restart.html
3.71
KB
-rw-r--r--
npm-restart.md
757
B
-rw-r--r--
npm-root.html
3.05
KB
-rw-r--r--
npm-root.md
275
B
-rw-r--r--
npm-run-script.html
6.54
KB
-rw-r--r--
npm-run-script.md
3.08
KB
-rw-r--r--
npm-search.html
6.07
KB
-rw-r--r--
npm-search.md
2.71
KB
-rw-r--r--
npm-shrinkwrap.html
3.65
KB
-rw-r--r--
npm-shrinkwrap.md
690
B
-rw-r--r--
npm-star.html
3.13
KB
-rw-r--r--
npm-star.md
461
B
-rw-r--r--
npm-stars.html
3.14
KB
-rw-r--r--
npm-stars.md
458
B
-rw-r--r--
npm-start.html
3.48
KB
-rw-r--r--
npm-start.md
586
B
-rw-r--r--
npm-stop.html
3.02
KB
-rw-r--r--
npm-stop.md
271
B
-rw-r--r--
npm-team.html
4.59
KB
-rw-r--r--
npm-team.md
1.78
KB
-rw-r--r--
npm-test.html
3.04
KB
-rw-r--r--
npm-test.md
296
B
-rw-r--r--
npm-token.html
5.4
KB
-rw-r--r--
npm-token.md
2.74
KB
-rw-r--r--
npm-uninstall.html
4.46
KB
-rw-r--r--
npm-uninstall.md
1.35
KB
-rw-r--r--
npm-unpublish.html
4.15
KB
-rw-r--r--
npm-unpublish.md
1.22
KB
-rw-r--r--
npm-update.html
6.92
KB
-rw-r--r--
npm-update.md
2.98
KB
-rw-r--r--
npm-version.html
7.96
KB
-rw-r--r--
npm-version.md.gz
1.82
KB
-rw-r--r--
npm-view.html
6.14
KB
-rw-r--r--
npm-view.md
2.93
KB
-rw-r--r--
npm-whoami.html
2.97
KB
-rw-r--r--
npm-whoami.md
268
B
-rw-r--r--
npm.html
9.39
KB
-rw-r--r--
npm.md.gz
2.37
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : npm-outdated.md
npm-outdated(1) -- Check for outdated packages ============================================== ## SYNOPSIS npm outdated [[<@scope>/]<pkg> ...] ## DESCRIPTION This command will check the registry to see if any (or, specific) installed packages are currently outdated. In the output: * `wanted` is the maximum version of the package that satisfies the semver range specified in `package.json`. If there's no available semver range (i.e. you're running `npm outdated --global`, or the package isn't included in `package.json`), then `wanted` shows the currently-installed version. * `latest` is the version of the package tagged as latest in the registry. Running `npm publish` with no special configuration will publish the package with a dist-tag of `latest`. This may or may not be the maximum version of the package, or the most-recently published version of the package, depending on how the package's developer manages the latest dist-tag(1). * `location` is where in the dependency tree the package is located. Note that `npm outdated` defaults to a depth of 0, so unless you override that, you'll always be seeing only top-level dependencies that are outdated. * `package type` (when using `--long` / `-l`) tells you whether this package is a `dependency` or a `devDependency`. Packages not included in `package.json` are always marked `dependencies`. ### An example ``` $ npm outdated Package Current Wanted Latest Location glob 5.0.15 5.0.15 6.0.1 test-outdated-output nothingness 0.0.3 git git test-outdated-output npm 3.5.1 3.5.2 3.5.1 test-outdated-output local-dev 0.0.3 linked linked test-outdated-output once 1.3.2 1.3.3 1.3.3 test-outdated-output ``` With these `dependencies`: ```json { "glob": "^5.0.15", "nothingness": "github:othiym23/nothingness#master", "npm": "^3.5.1", "once": "^1.3.1" } ``` A few things to note: * `glob` requires `^5`, which prevents npm from installing `glob@6`, which is outside the semver range. * Git dependencies will always be reinstalled, because of how they're specified. The installed committish might satisfy the dependency specifier (if it's something immutable, like a commit SHA), or it might not, so `npm outdated` and `npm update` have to fetch Git repos to check. This is why currently doing a reinstall of a Git dependency always forces a new clone and install. * `npm@3.5.2` is marked as "wanted", but "latest" is `npm@3.5.1` because npm uses dist-tags to manage its `latest` and `next` release channels. `npm update` will install the _newest_ version, but `npm install npm` (with no semver range) will install whatever's tagged as `latest`. * `once` is just plain out of date. Reinstalling `node_modules` from scratch or running `npm update` will bring it up to spec. ## CONFIGURATION ### json * Default: false * Type: Boolean Show information in JSON format. ### long * Default: false * Type: Boolean Show extended information. ### parseable * Default: false * Type: Boolean Show parseable output instead of tree view. ### global * Default: false * Type: Boolean Check packages in the global install prefix instead of in the current project. ### depth * Default: 0 * Type: Int Max depth for checking dependency tree. ## SEE ALSO * npm-update(1) * npm-dist-tag(1) * npm-registry(7) * npm-folders(5)
Close
