Linux server2.hpierson.com 3.10.0-1160.105.1.el7.x86_64 #1 SMP Thu Dec 7 15:39:45 UTC 2023 x86_64
Apache
: 162.0.216.123 | : 216.73.216.152
28 Domain
?7.4.33
yvffpqmy
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
README
+ Create Folder
+ Create File
/
usr /
lib /
node_modules /
npm /
man /
man5 /
[ HOME SHELL ]
Name
Size
Permission
Action
folders.5
1.77
KB
-rw-r--r--
install.5
3.13
KB
-rw-r--r--
npmrc.5
3
KB
-rw-r--r--
package-json.5
28.54
KB
-rw-r--r--
package-lock-json.5
5.99
KB
-rw-r--r--
package-locks.5
6.84
KB
-rw-r--r--
shrinkwrap-json.5
1.24
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : folders.5
.P [E] ``` .P Since foo depends directly on \fBbar@1\.2\.3\fP and \fBbaz@1\.2\.3\fP, those are installed in foo's \fBnode_modules\fP folder\. .P Even though the latest copy of blerg is 1\.3\.7, foo has a specific dependency on version 1\.2\.5\. So, that gets installed at [A]\. Since the parent installation of blerg satisfies bar's dependency on \fBblerg@1\.x\fP, it does not install another copy under [B]\. .P Bar [B] also has dependencies on baz and asdf, so those are installed in bar's \fBnode_modules\fP folder\. Because it depends on \fBbaz@2\.x\fP, it cannot re\-use the \fBbaz@1\.2\.3\fP installed in the parent \fBnode_modules\fP folder [D], and must install its own copy [C]\. .P Underneath bar, the \fBbaz \-> quux \-> bar\fP dependency creates a cycle\. However, because bar is already in quux's ancestry [B], it does not unpack another copy of bar into that folder\. .P Underneath \fBfoo \-> baz\fP [D], quux's [E] folder tree is empty, because its dependency on bar is satisfied by the parent folder copy installed at [B]\. .P For a graphical breakdown of what is installed where, use \fBnpm ls\fP\|\. .SS Publishing .P Upon publishing, npm will look in the \fBnode_modules\fP folder\. If any of the items there are not in the \fBbundledDependencies\fP array, then they will not be included in the package tarball\. .P This allows a package maintainer to install all of their dependencies (and dev dependencies) locally, but only re\-publish those items that cannot be found elsewhere\. See npm help \fBpackage\.json\fP for more information\. .SS See also .RS 0 .IP \(bu 2 npm help package\.json .IP \(bu 2 npm help install .IP \(bu 2 npm help pack .IP \(bu 2 npm help cache .IP \(bu 2 npm help config .IP \(bu 2 npm help npmrc .IP \(bu 2 npm help config .IP \(bu 2 npm help publish .RE
Close