A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/npm/npm/commit/f8e76d8566ae1965e57d348df74edad0643b66a6 below:

Correct Windows prefix path in npm-folders docs. · npm/npm@f8e76d8 · GitHub

This repository was archived by the owner on Aug 11, 2022. It is now read-only.

File tree Expand file treeCollapse file tree 1 file changed

+3

-4

lines changed

Filter options

Expand file treeCollapse file tree 1 file changed

+3

-4

lines changed Original file line number Diff line number Diff line change

@@ -20,10 +20,9 @@ This document will tell you what it puts where.

20 20

### prefix Configuration

21 21 22 22

The `prefix` config defaults to the location where node is installed.

23 -

On most systems, this is `/usr/local`. On windows, this is the exact

24 -

location of the node.exe binary. On Unix systems, it's one level up,

25 -

since node is typically installed at `{prefix}/bin/node` rather than

26 -

`{prefix}/node.exe`.

23 +

On most systems, this is `/usr/local`. On Windows, it's `%AppData%\npm`.

24 +

On Unix systems, it's one level up, since node is typically installed at

25 +

`{prefix}/bin/node` rather than `{prefix}/node.exe`.

27 26 28 27

When the `global` flag is set, npm installs things into this prefix.

29 28

When it is not set, it uses the root of the current package, or the

You can’t perform that action at this time.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4