blocks|key|2552262|text|为了方便起见，创建了n个模块。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2552263|例如，如果您想将您的Node.js版本从v0.8.0更新到v0.10.20，您愿意下载包、解压缩和编译吗？还是您更愿意输入n+0.10.20并立即安装它，同时仍然保留以前的Node版本以便于切换？|offset|length|style|CODE|2552264|N建议使用npm来安装它，因为n是一个模块。也就是说，npm是安装它的最简单的方法。节点模块具有在全局安装时能够在shell中运行的功能，因此该功能被用来使切换Node版本更加容易。|2552265|entityMap^0|0|1P|9|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

The n module was created for convenience.

For example, if you wanted to update your version of Node.js from v0.8.0 to v0.10.20, would you rather download a package, extract and compile? Or would you rather type <code>n 0.10.20</code> and have it instantly installed, while still retaining previous versions of Node for easy switching?

n suggests using npm to install it because n is a module. That is, npm is the easiest way to install it. Node modules have the functionality of being able to run in a shell when installed globally, so that function was utilized to make switching Node versions much easier.

blocks|key|2552283|text|如果您愿意，可以从源安装n：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2552284|cd+/tmp
git+clone+--depth=1+https://github.com/tj/n
cd+n
sudo+make+install|code-block|syntax|javascript|2552285|然后，您可以按以下方式安装节点的最新稳定版本：|2552286|n+stable|2552287|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

If you prefer, you can install n from source:

<pre><code>cd /tmp
git clone --depth=1 https://github.com/tj/n
cd n
sudo make install
</code></pre>

Then you can install the latest stable version of node as follows:

<pre><code>n stable
</code></pre>

blocks|key|1475405|text|您还可以将npm与Node.JS分开安装；例如:在没有Node.JS的系统上：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1475406|git+clone+https://github.com/npm/npm
cd+npm
./configure
make|code-block|syntax|javascript|1475407|参考资料：NPM+GitHub项目|1475408|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/npm/npm^0|5|3|0|0|5|C|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

You can also install <code>npm</code> separately from Node.JS; e.g.: on a system without Node.JS:

<pre><code>git clone https://github.com/npm/npm
cd npm
./configure
make
</code></pre>

Reference: <a href="https://github.com/npm/npm" rel="nofollow">NPM GitHub project</a>

blocks|key|2552380|text|我也有同样的问题，但我看到了光明。'n‘是一个方便的工具，它使得测试不同版本的节点变得很简单。在Linux上工作很好，但是无论我如何尝试在OS上安装它(git克隆，然后是npm安装或使用user456584的推荐方法)，当我运行它时，我总是得到相同的结果：“错误:没有安装的版本”，即使它安装到|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2552381|/usr/local/lib/节点_模块/n|blockquote|2552382|和|2552383|/usr/local/bin/n|2552384|令人沮丧的是，我发现这个工具在Linux上非常方便。|2552385|entityMap^0|2L|A|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$]]|$1|I|3|J|5|6|7|U|8|@]|D|@]|E|$]]|$1|K|3|L|5|H|7|V|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|W|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|P|$]]

I had the same question, but have seen the light. 'n' is a handy tool and makes it simple to test different versions of node. Works great on Linux, but no matter how I try to install it on OS X (git clone, then npm install or using user456584's recommended method), when I run it, I always get the same results of "Error: no installed version", even though it installs into 

<blockquote>
 /usr/local/lib/node_modules/n
</blockquote>

and 

<blockquote>
 /usr/local/bin/n
</blockquote>

Frustrating because I've found this tool to be so handy on Linux.

blocks|key|1475515|text|tl；博士|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1475516|#+Installs+n+and+the+latest+LTS+Node.js+version+to+~/n.
#+For+bash,+ksh,+zsh,+modifies+the+respective+user-specific+shell-initialization+file+to
#+define+env.+variable+N_PREFIX+and+append+$N_PREFIX/bin+to+the+$PATH.
curl+-L+https://git.io/n-install+%7C+bash++|code-block|syntax|javascript|1475517|我感觉到你的痛苦。安装Node.js然后安装n然后管理Node.js安装确实是一个奇怪的设置。|CODE|1475518|如果能够先安装n，那就太好了。|1475519|我已经创建了一个n+来直接从GitHub支持的安装；除了n本身所需要的之外，唯一的先决条件是+git.|1475520|请注意，您必须首先删除任何预先存在的n+/+Node.js版本。|1475521|默认情况下，目标目录(+~/n+)必须不存在或为空。|1475522|对于bash、ksh和zsh，相关的shell初始化文件(例如~/.bashrc)会被自动修改，以定义环境变量N_PREFIX并将$N_PREFIX/bin附加到$PATH中；对于其他shell，这必须手动完成。|1475523|除了直接从n安装GitHub之外，它还安装了用于更新n+(n-update)和卸载它的助手脚本(n-uninstall)。|1475524|下面是工作示例；有关详细信息，请参阅N-安装GitHub回购：|1475525|安装带有确认提示的安装，以确认安装到默认位置$HOME/n并安装最新的LTS+Node.js版本：
卷曲-L+https://git.io/n-install+bash|unordered-list-item|1475526|自动安装到默认位置，随后安装最新的LTS+(长期支持)和最新的总体Node.js版本，以及最新的4.1.x+Node.js版本：
curl+-L+https://git.io/n-install+bash+-s+-y+lts最新4.1|1475527|自动安装到默认位置，无需随后安装Node.js版本：
卷发-L+https://git.io/n-install+bash+-s+-y+-|1475528|自动安装到自定义位置~/util/n，随后安装最新的LTS+Node.js版本：
curl+-L+https://git.io/n-install+https://git.io/n-installN_前缀=~/util/n+bash+-s+-y|1475529|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/mklement0/n-install|1|https://git.io/n-install|2|3|4|5^0|0|3|0|0|M|1|0|7|1|0|8|1|A|A|M|O|1B|4|8|1|S|1|1B|3|0|0|W|I|1|0|0|Q|C|3|0|0|2Y|2|4|7|3|B|3|V|9|1J|8|1T|D|29|5|0|0|1P|5|1|Q|1|T|8|1C|B|0|0|V|I|C|0|0|0|1D|1E|Y|M|7|1J|O|1|0|0|1S|1T|1G|21|O|2|0|0|Q|R|16|W|O|3|0|0|14|15|W|22|1C|A|8|1D|O|4|22|O|5|0^^$0|@$1|2|3|4|5|6|7|1O|8|@$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1S|8|@$9|1T|A|1U|B|M]]|D|@]|E|$]]|$1|N|3|O|5|6|7|1V|8|@$9|1W|A|1X|B|M]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1Y|8|@$9|1Z|A|20|B|C]|$9|21|A|22|B|C]|$9|23|A|24|B|C]|$9|25|A|26|B|C]|$9|27|A|28|B|M]|$9|29|A|2A|B|M]|$9|2B|A|2C|B|M]]|D|@]|E|$]]|$1|R|3|S|5|6|7|2D|8|@$9|2E|A|2F|B|C]|$9|2G|A|2H|B|M]]|D|@]|E|$]]|$1|T|3|U|5|6|7|2I|8|@$9|2J|A|2K|B|C]|$9|2L|A|2M|B|M]]|D|@]|E|$]]|$1|V|3|W|5|6|7|2N|8|@$9|2O|A|2P|B|C]|$9|2Q|A|2R|B|M]|$9|2S|A|2T|B|M]|$9|2U|A|2V|B|M]|$9|2W|A|2X|B|M]|$9|2Y|A|2Z|B|M]|$9|30|A|31|B|M]|$9|32|A|33|B|M]]|D|@]|E|$]]|$1|X|3|Y|5|6|7|34|8|@$9|35|A|36|B|C]|$9|37|A|38|B|M]|$9|39|A|3A|B|M]|$9|3B|A|3C|B|M]|$9|3D|A|3E|B|M]]|D|@]|E|$]]|$1|Z|3|10|5|6|7|3F|8|@$9|3G|A|3H|B|C]]|D|@$9|3I|A|3J|1|3K]]|E|$]]|$1|11|3|12|5|13|7|3L|8|@$9|3M|A|3N|B|C]|$9|3O|A|3P|B|C]|$9|3Q|A|3R|B|M]]|D|@$9|3S|A|3T|1|3U]]|E|$]]|$1|14|3|15|5|13|7|3V|8|@$9|3W|A|3X|B|C]|$9|3Y|A|3Z|B|C]]|D|@$9|40|A|41|1|42]]|E|$]]|$1|16|3|17|5|13|7|43|8|@$9|44|A|45|B|C]|$9|46|A|47|B|C]]|D|@$9|48|A|49|1|4A]]|E|$]]|$1|18|3|19|5|13|7|4B|8|@$9|4C|A|4D|B|C]|$9|4E|A|4F|B|C]|$9|4G|A|4H|B|C]|$9|4I|A|4J|B|M]]|D|@$9|4K|A|4L|1|4M]|$9|4N|A|4O|1|4P]]|E|$]]|$1|1A|3|-4|5|6|7|4Q|8|@]|D|@]|E|$]]]|1B|$1C|$5|1D|1E|1F|E|$1G|1H]]|1I|$5|1D|1E|1F|E|$1G|1J]]|1K|$5|1D|1E|1F|E|$1G|1J]]|1L|$5|1D|1E|1F|E|$1G|1J]]|1M|$5|1D|1E|1F|E|$1G|1J]]|1N|$5|1D|1E|1F|E|$1G|1J]]]]

tl; dr



<pre class="lang-sh prettyprint-override"><code># Installs n and the latest LTS Node.js version to ~/n.
# For bash, ksh, zsh, modifies the respective user-specific shell-initialization file to
# define env. variable N_PREFIX and append $N_PREFIX/bin to the $PATH.
curl -L https://git.io/n-install | bash 
</code></pre>

<hr>

I feel your pain. Installing Node.js to then install <code>n</code> to then manage Node.js installations is indeed a strange setup.

It would indeed be great to be able to install <code>n</code> by itself first.

I've created a <a href="https://github.com/mklement0/n-install" rel="noreferrer">project</a> to support installation of <code>n</code> directly from GitHub; the only prerequisite beyond what <code>n</code> itself needs is <code>git</code>.

Note that you must first remove any pre-existing <code>n</code> / Node.js versions. 
The target directory, <code>~/n</code> by default, must either not yet exist or be empty. 
For <code>bash</code>, <code>ksh</code>, and <code>zsh</code>, the relevant shell initialization file (e.g., <code>~/.bashrc</code>) is automatically modified to define environment variable <code>N_PREFIX</code> and append <code>$N_PREFIX/bin</code> to the <code>$PATH</code>; for other shells, this must be done manually.

Aside from installing <code>n</code> directly from GitHub, it also installs helper scripts for updating <code>n</code> (<code>n-update</code>) and uninstalling it (<code>n-uninstall</code>).

Here are working examples; see the <a href="https://github.com/mklement0/n-install" rel="noreferrer">n-install GitHub repo</a> for details:

<ul>
<li>Installation with confirmation prompt to confirm installing to default location <code>$HOME/n</code> and installing the latest LTS Node.js version:

<pre class="lang-sh prettyprint-override"><code>curl -L https://git.io/n-install | bash
</code></pre></li>
<li>Automated installation to the default location, with subsequent installation of the latest LTS (long-term support) and latest-overall Node.js versions, as well as the latest 4.1.x Node.js version:

<pre class="lang-sh prettyprint-override"><code>curl -L https://git.io/n-install | bash -s -- -y lts latest 4.1
</code></pre></li>
<li>Automated installation to the default location, without subsequent installation of a Node.js version:

<pre class="lang-sh prettyprint-override"><code>curl -L https://git.io/n-install | bash -s -- -y -
</code></pre></li>
<li>Automated installation to custom location <code>~/util/n</code>, with subsequent installation of the latest LTS Node.js version:

<pre class="lang-sh prettyprint-override"><code>curl -L https://git.io/n-install | N_PREFIX=~/util/n bash -s -- -y
</code></pre></li>
</ul>

blocks|key|2552451|text|如果您在$PATH变量中包含了默认节点bin，如下所示|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2552452|export+PATH=/usr/local/Cellar/node/11.5.0/bin:$PATH|code-block|syntax|javascript|2552453|然后，n将无法激活其他节点版本。从路径中删除此导出，然后可以通过n管理当前活动节点版本。|2552454|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If you have included your default node bin in the $PATH variable like this

<pre><code>export PATH=/usr/local/Cellar/node/11.5.0/bin:$PATH
</code></pre>

then n will not be able to active other node versions. Remove this export from the path and then you can manage the currently active node version by n.

blocks|key|2552473|text|如果您使用的是n，那么应该使用以下命令|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2552474|bash$+sudo最新|2552475|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you are using n then you should use below command
bash$ sudo n latest

blocks|key|2552533|text|n的自述文件现在有一个较长的章节，涵盖了不同的安装方法。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2552534|和nvm一样，n是一个bash脚本。如果您已经拥有npm，则建议使用n作为安装npm的简单方法，然后可以使用n更改Node.js版本。但是第一次安装Node.js还有很多其他的方法。总之，没有什么特别的顺序.|2552535|您可以使用curl安装n：|2552536|curl+-L+https://raw.githubusercontent.com/tj/n/master/bin/n+-o+n|code-block|syntax|javascript|2552537|或者克隆n回购并从那里安装：|2552538|make+install|2552539|或者使用N-安装|2552540|curl+-L+https://git.io/n-install+%7C+bash|2552541|或自制软件|2552542|brew+install+n|2552543|或MacPorts|2552544|port+install+n|2552545|(免责声明:我是n目前的维护者。)|2552546|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/tj/n#installation|1|https://github.com/mklement0/n-install|2|https://brew.sh/|3|https://www.macports.org/^0|0|1|N|2|0|0|1|3|7|1|P|3|Y|1|13|3|1I|1|0|B|1|0|0|4|1|0|0|4|4|1|0|0|1|4|2|0|0|1|8|3|0|0|8|1|0^^$0|@$1|2|3|4|5|6|7|1K|8|@$9|1L|A|1M|B|C]]|D|@$9|1N|A|1O|1|1P]]|E|$]]|$1|F|3|G|5|6|7|1Q|8|@$9|1R|A|1S|B|C]|$9|1T|A|1U|B|C]|$9|1V|A|1W|B|C]|$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|C]|$9|21|A|22|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|23|8|@$9|24|A|25|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|26|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|27|8|@$9|28|A|29|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|L|7|2A|8|@]|D|@]|E|$M|N]]|$1|S|3|T|5|6|7|2B|8|@]|D|@$9|2C|A|2D|1|2E]]|E|$]]|$1|U|3|V|5|L|7|2F|8|@]|D|@]|E|$M|N]]|$1|W|3|X|5|6|7|2G|8|@]|D|@$9|2H|A|2I|1|2J]]|E|$]]|$1|Y|3|Z|5|L|7|2K|8|@]|D|@]|E|$M|N]]|$1|10|3|11|5|6|7|2L|8|@]|D|@$9|2M|A|2N|1|2O]]|E|$]]|$1|12|3|13|5|L|7|2P|8|@]|D|@]|E|$M|N]]|$1|14|3|15|5|6|7|2Q|8|@$9|2R|A|2S|B|C]]|D|@]|E|$]]|$1|16|3|-4|5|6|7|2T|8|@]|D|@]|E|$]]]|17|$18|$5|19|1A|1B|E|$1C|1D]]|1E|$5|19|1A|1B|E|$1C|1F]]|1G|$5|19|1A|1B|E|$1C|1H]]|1I|$5|19|1A|1B|E|$1C|1J]]]]

The README for <code>n</code> now has a longer section covering different <a href="https://github.com/tj/n#installation" rel="nofollow noreferrer">installation</a> approaches.
Like <code>nvm</code>, <code>n</code> is a bash script. <code>npm</code> is suggested as an easy way to install <code>n</code> if you already have <code>npm</code>, and then you can use <code>n</code> to change the Node.js version. But there are plenty of other approaches for a first install of Node.js. In brief and in no particular order...
You can install <code>n</code> using curl:
<pre><code>curl -L https://raw.githubusercontent.com/tj/n/master/bin/n -o n
</code></pre>
Or clone the <code>n</code> repo and install from there:
<pre><code>make install
</code></pre>
Or use <a href="https://github.com/mklement0/n-install" rel="nofollow noreferrer">n-install</a>:
<pre><code>curl -L https://git.io/n-install | bash
</code></pre>
Or <a href="https://brew.sh/" rel="nofollow noreferrer">Homebrew</a>:
<pre><code>brew install n
</code></pre>
Or <a href="https://www.macports.org/" rel="nofollow noreferrer">MacPorts</a>:
<pre><code>port install n
</code></pre>
(Disclaimer: I am the current maintainer of <code>n</code>.)

I have a problem understanding the use of <a href="https://github.com/visionmedia/n" rel="noreferrer">n</a>. Basically, it is clear that it is a version manager for Node.js such as <a href="https://github.com/creationix/nvm" rel="noreferrer">nvm</a>.

But in contrast to nvm, which is basically a shell script, according to the documentation you are encouraged to use npm to install n:

<pre><code>$ npm install -g n
</code></pre>

What I don't get is: For having <code>npm</code> at hand you need to install Node.js. Why would I install Node.js manually to use <code>npm</code> to then be able to install Node.js using n?

To put my question in other words: Why does n suggest installing using <code>npm</code>, if its main purpose is to install Node.js, which includes npm?

Install Node.js to install n to install Node.js?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我很难理解的使用。基本上，很明显，它是Node.js的版本管理器，比如。但是与nvm相比，nvm基本上是一个shell脚本，根据文档，我们鼓励您使用npm安装n。$ npm install -g n我不明白的是:如果手头有npm，您需要安装Node.js。为什么我要手动安装Node.js以使用npm才能使用n安装Nod...

问安装Node.js以安装n以安装Node.js？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问安装Node.js以安装n以安装Node.js？EN