Lines Matching full:folder
140 <span class="description">Folder Structures Used by npm</span>
145 …tallation</a></li><li><a href="#cycles-conflicts-and-folder-parsimony">Cycles, Conflicts, and Fold…
170 <p>Packages are dropped into the <code>node_modules</code> folder under the <code>prefix</code>.
176 <code>lib</code> folder.)</p>
178 in a sub-folder of the relevant <code>node_modules</code> folder with the name of that
200 <p>Temporary files are stored by default in the folder specified by the
203 <p>Temp files are given a unique folder under this root for each run of the
207 <code>prefix</code> folder. This is so that <code>npm install foo@1.2.3</code> will install
209 into some other folder.</p>
210 <p>Starting at the $PWD, npm will walk up the folder tree checking for a
211 folder that contains either a <code>package.json</code> file, or a <code>node_modules</code>
212 folder. If such a thing is found, then that is treated as the effective
214 behavior is inspired by and similar to git's .git-folder seeking
216 <p>If no package root is found, then the current folder is used.</p>
228 <h4 id="cycles-conflicts-and-folder-parsimony">Cycles, Conflicts, and Folder Parsimony</h4>
232 folder, then it is not installed at the current location.</p>
235 <code>foo -> bar -> baz -> bar -> baz ...</code>. However, since the folder
247 highest level possible, below the localized "target" folder (hoisting).
263 <p>In this case, we might expect a folder structure like this
276 installed in foo's <code>node_modules</code> folder.</p>
282 re-use the <code>baz@1.2.3</code> installed in the parent <code>node_modules</code> folder [D],
287 unpack another copy of bar into that folder. Likewise, quux's [E]
288 folder tree is empty, because its dependency on bar is satisfied
289 by the parent folder copy installed at [B].</p>
292 <p>Upon publishing, npm will look in the <code>node_modules</code> folder. If any of