blocks|key|152468|text|从npm+7开始，这些命令更加简单：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|152469|npm+ls+--link+--global|offset|length|style|CODE|152470|Local模块：npm+ls+--link|unordered-list-item|152471|
+|152472|全局模块|152473|152474|因发现--link标志而归功于Andrew|152475|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/332988/andrew^0|0|0|M|0|8|D|0|0|0|0|3|6|F|6|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|A|$]]|$1|M|3|N|5|J|7|17|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@$D|1C|E|1D|1|1E]]|A|$]]|$1|R|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

These commands are simpler as of npm 7:
<ul>
<li>Global modules: <code>npm ls --link --global</code></li>
<li>Local modules: <code>npm ls --link</code></li>
</ul>
Credit to <a href="https://stackoverflow.com/users/332988/andrew">Andrew</a> for finding the <code>--link</code> flag

blocks|key|153789|text|要列出所有全局链接的模块，请执行以下操作(documentation+https://docs.npmjs.com/cli/ls)：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|153790|npm+ls+-g+--depth=0+--link=true|code-block|syntax|javascript|153791|不过，我必须先更新机器上的npm版本：|153792|npm+install+npm@latest+-g|153793|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.npmjs.com/cli/ls^0|Z|T|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

To list all globally linked modules, this works (documentation <a href="https://docs.npmjs.com/cli/ls" rel="noreferrer">https://docs.npmjs.com/cli/ls</a>):

<pre><code>npm ls -g --depth=0 --link=true
</code></pre>

I had to update the version of npm on my machine first, though:

<pre><code>npm install npm@latest -g
</code></pre>

blocks|key|2734219|text|您是否尝试过仅列出node_modules目录内容(例如，ls+-l+node_modules+%7C+grep+%5El)？它们是普通的符号链接。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2734220|如果你真的需要找到所有的符号链接，你可以尝试像find+/+-type+d+-name+"node_modules"+2>/dev/null+%7C+xargs+-I{}+find+{}+-type+l+-maxdepth+1+%7C+xargs+ls+-l这样的东西。|2734221|entityMap^0|9|C|T|S|0|N|2U|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

Did you try just listing the <code>node_modules</code> directory contents (e.g., <code>ls -l node_modules | grep ^l</code>)? They're normal symbolic links.
If you really need to find all symbolic links, you could try something like <code>find / -type d -name &quot;node_modules&quot; 2&gt;/dev/null | xargs -I{} find {} -type l -maxdepth 1 | xargs ls -l</code>.

blocks|key|149625|text|解析ls的一种更好的替代方法是像这样使用find：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|149626|find+.+-type+l|code-block|syntax|javascript|149627|您可以使用-maxdepth+1仅处理第一个目录级别：|149628|find+.+-maxdepth+1+-type+l|149629|您可以使用-ls获取更多信息。|149630|例如，要查找与npm链接的Node.js模块：|149631|find+node_modules+-maxdepth+1+-type+l+-ls|149632|Here's++为什么解析+ls+不是最好的想法。|BOLD|149633|entityMap^0|2|2|K|4|0|0|5|B|0|0|5|3|0|0|0|0|6|8|5|E|2|E|2|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|18|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1C|8|@]|D|@]|E|$]]|$1|S|3|T|5|H|7|1D|8|@]|D|@]|E|$I|J]]|$1|U|3|V|5|6|7|1E|8|@$9|1F|A|1G|B|W]|$9|1H|A|1I|B|W]|$9|1J|A|1K|B|W]|$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|X|3|-4|5|6|7|1N|8|@]|D|@]|E|$]]]|Y|$]]

A better alternative to parsing <code>ls</code> is to use <code>find</code> like this:
<pre><code>find . -type l
</code></pre>
You can use <code>-maxdepth 1</code> to only process the first directory level:
<pre><code>find . -maxdepth 1 -type l
</code></pre>
You can use <code>-ls</code> for additional information.
For instance, for finding Node.js modules that are npm linked:
<pre><code>find node_modules -maxdepth 1 -type l -ls
</code></pre>
Here's <a href="http://mywiki.wooledge.org/ParsingLs" rel="nofollow noreferrer">an article</a> why parsing <code>ls</code> is not the best idea.

blocks|key|150937|text|如果你想从npm+list得到一个漂亮的彩色输出，你可以这样做：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|150938|\ls+-F+node_modules+%7C+sed+-n+'s/@$//p'+%7C+xargs+npm+ls+-g+--depth+0|code-block|syntax|javascript|150939|它给出了我当前的游乐场目录：|150940|%2B--+color@0.11.1
%2B--+grunt@0.4.5
%2B--+http-server@0.8.5
%2B--+jsdom@8.0.2
%2B--+jsonfile@2.2.3
%2B--+underscore@1.8.3
%2B--+xmlserializer@0.3.3
`--+zombie@4.2.1|150941|它做了一些假设，但它应该在大多数情况下都能工作，或者很容易适应下面的解释。|150942|150943|使用\ls绕过ls命令上可能的别名|unordered-list-item|150944|+-F选项为链接添加一个'@‘指示符<+module.|150945|-g+>d12命令选择这些链接并删除|150946|xargs部分将以前的输出作为参数传递给使用|150947|list或ls调用的|150948|，以使用<-F>d26-F>列出模块以获取有关列出的每个全局模块的module.|150949|-g和H230的详细信息用于浅层列表(optional)|150950|--long+false的code>|150951|--depth+0+(默认与'list').|150952|一起使用|150953|问题:出于某些原因，npm目前为我提供了无关的条目(非彩色)。它们将是那些我已经"npm+unlink“编辑的。|150954|对于当前npm路径中的“所有全局安装的模块列表”，您只需执行以下操作|150955|npm+list+-g|150956|对于更多的需求，您可能想要看看|150957|npm+help+folders|150958|除非扫描整个文件系统(这不是npm特有的问题)，否则不能向后跟踪符号链接。|150959|为了快速按名称查找文件和目录，我使用locate，它通常每天重建一次索引。|150960|locate+'*/node_modules'|150961|并从那里开始工作(您可能希望使用--regexp选项优化搜索。|150962|entityMap^0|5|8|0|0|0|0|0|0|2|3|7|2|0|1|2|0|0|2|0|0|5|1|0|4|5|2|1|5|2|1|0|2|3|P|1|0|I|1|0|M|1|0|4|0|0|1K|0|0|Y|0|0|0|F|0|0|0|11|0|0|11|0|0|0|V|0^^$0|@$1|2|3|4|5|6|7|1W|8|@$9|1X|A|1Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|20|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|21|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|22|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|23|8|@]|D|@]|E|$]]|$1|R|3|S|5|T|7|24|8|@$9|25|A|26|B|C]|$9|27|A|28|B|C]]|D|@]|E|$]]|$1|U|3|V|5|T|7|29|8|@$9|2A|A|2B|B|C]]|D|@]|E|$]]|$1|W|3|X|5|T|7|2C|8|@$9|2D|A|2E|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|2F|8|@$9|2G|A|2H|B|C]]|D|@]|E|$]]|$1|10|3|11|5|T|7|2I|8|@$9|2J|A|2K|B|C]|$9|2L|A|2M|B|C]]|D|@]|E|$]]|$1|12|3|13|5|T|7|2N|8|@$9|2O|A|2P|B|C]]|D|@]|E|$]]|$1|14|3|15|5|T|7|2Q|8|@$9|2R|A|2S|B|C]|$9|2T|A|2U|B|C]]|D|@]|E|$]]|$1|16|3|17|5|T|7|2V|8|@$9|2W|A|2X|B|C]]|D|@]|E|$]]|$1|18|3|19|5|T|7|2Y|8|@$9|2Z|A|30|B|C]]|D|@]|E|$]]|$1|1A|3|1B|5|6|7|31|8|@$9|32|A|33|B|C]]|D|@]|E|$]]|$1|1C|3|1D|5|6|7|34|8|@$9|35|A|36|B|C]]|D|@]|E|$]]|$1|1E|3|1F|5|6|7|37|8|@$9|38|A|39|B|C]]|D|@]|E|$]]|$1|1G|3|1H|5|H|7|3A|8|@]|D|@]|E|$I|J]]|$1|1I|3|1J|5|6|7|3B|8|@$9|3C|A|3D|B|C]]|D|@]|E|$]]|$1|1K|3|1L|5|H|7|3E|8|@]|D|@]|E|$I|J]]|$1|1M|3|1N|5|6|7|3F|8|@$9|3G|A|3H|B|C]]|D|@]|E|$]]|$1|1O|3|1P|5|6|7|3I|8|@$9|3J|A|3K|B|C]]|D|@]|E|$]]|$1|1Q|3|1R|5|H|7|3L|8|@]|D|@]|E|$I|J]]|$1|1S|3|1T|5|6|7|3M|8|@$9|3N|A|3O|B|C]]|D|@]|E|$]]|$1|1U|3|-4|5|6|7|3P|8|@]|D|@]|E|$]]]|1V|$]]

If you want a nice colored output from <code>npm list</code>, you may like:
<pre><code>\ls -F node_modules | sed -n 's/@$//p' | xargs npm ls -g --depth 0
</code></pre>
which gives in my current playground directory:
<pre><code>+-- color@0.11.1
+-- grunt@0.4.5
+-- http-server@0.8.5
+-- jsdom@8.0.2
+-- jsonfile@2.2.3
+-- underscore@1.8.3
+-- xmlserializer@0.3.3
`-- zombie@4.2.1
</code></pre>
It makes a few assumptions, but it should work in most cases, or be easy to adapt with the explanations below.
<ul>
<li>use <code>\ls</code> to bypass possible aliases on your <code>ls</code> command</li>
<li>the <code>-F</code> option adds an '@' indicator for links</li>
<li>the <code>sed</code> command selects those links and removes the indicator</li>
<li>the <code>xargs</code> part passes previous output as arguments to <code>npm ...</code></li>
<li><code>npm</code> is invoked with
<ul>
<li><code>list</code> or <code>ls</code> to list modules with versions</li>
<li>replace with <code>ll</code> to get details about each listed module.</li>
<li><code>-g</code> for the global modules and</li>
<li><code>--depth 0</code> for a shallow listing (optional)</li>
<li><code>--long false</code> (default with 'list').</li>
</ul>
</li>
</ul>
Issue: for some reason npm gives extraneous entries for me at the moment (non colored). They would be those I had &quot;npm unlink&quot;ed.
For &quot;a list of all globally installed modules&quot; in current npm path, you just do
<pre><code>npm list -g
</code></pre>
For further needs you may want to have a look at
<pre><code>npm help folders
</code></pre>
You cannot follow symlinks backwards unless you scan your whole filesystem and (then that's not a npm specific question).
For quickly finding files and directories by name, I use <code>locate</code> which works on an index rebuilt usually once a day.
<pre><code>locate '*/node_modules'
</code></pre>
and start working from there (you may want to refine the search with <code>--regexp</code> option.

blocks|key|149638|text|我制作了一个Node.js模块，它使用fs检查由npm+link或其他方式创建的符号链接。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|149639|var+symlinked+=+require("symlinked")

console.log(symlinked.names())|code-block|syntax|javascript|149640|entityMap^0|J|2|O|8|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

I made a Node.js module, <a href="https://www.npmjs.com/package/symlinked" rel="nofollow noreferrer">symlinked</a>, that uses <code>fs</code> to check for symbolic links made by <code>npm link</code> or otherwise.
<pre><code>var symlinked = require(&quot;symlinked&quot;)

console.log(symlinked.names())
</code></pre>

blocks|key|2734404|text|在我也编写了自己的工具之后，我发现了这个问题，为了完整起见，这里是：npm-list-linked。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2734405|它还将递归地跟踪层次结构中所有链接的包。在我的工作中，我们有时可能有2-3层深的npm+link，这样你就可以准确地看到哪些是本地的，哪些不是本地的。它避免了意外。|style|CODE|2734406|npm-list-linked|code-block|syntax|javascript|2734407|输出：|2734408|Linked+packages+in+/home/user/projects/some-project/
++++@prefix/package+0.2.7
++++++++other-package+0.1.2|2734409|entityMap|0|LINK|mutability|MUTABLE|url|https://www.npmjs.com/package/npm-list-linked^0|Y|F|0|0|14|8|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@$A|13|B|14|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|15|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|16|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|17|8|@]|9|@]|C|$K|L]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

I found this question after I also wrote my own tool, and here it is for completeness: <a href="https://www.npmjs.com/package/npm-list-linked" rel="nofollow noreferrer">npm-list-linked</a>.
It will recursively follow all linked packages down in the hierarchy as well. At my work we sometimes may have <code>npm link</code> 2-3 levels deep and this way you can see exactly which are local and which ones are not. It avoids surprises.
<pre><code>npm-list-linked
</code></pre>
Output:
<pre class="lang-none prettyprint-override"><code>Linked packages in /home/user/projects/some-project/
 @prefix/package 0.2.7
 other-package 0.1.2
</code></pre>

blocks|key|149690|text|使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|149691|find+`npm+root+-g`+-maxdepth+2+-type+l|code-block|syntax|javascript|149692|以显示全局链接，包括命名空间包。|149693|Andrew's+answer在某些情况下可以工作：|offset|length|149694|npm+ls+-g+--depth=0+--link=true|149695|但在某些情况下，它会在我的同级依赖错误中爆发。|149696|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/24933955/how-to-list-all-the-node-js-modules-i-have-linked-with-npm/48593067#48593067^0|0|0|0|0|F|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|11|8|@]|9|@$K|12|L|13|1|14]]|A|$]]|$1|M|3|N|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

Use
<pre><code>find `npm root -g` -maxdepth 2 -type l
</code></pre>
to show global links, including namespaced packages.
<a href="https://stackoverflow.com/questions/24933955/how-to-list-all-the-node-js-modules-i-have-linked-with-npm/48593067#48593067">Andrew's answer</a> works some of the time:
<pre><code>npm ls -g --depth=0 --link=true
</code></pre>
But it blew up on peer dependency errors for me on some occasions.

blocks|key|149635|text|我看到我自己和其他人也经常有同样的问题。我为自己写了一个名为link-status的小命令行界面来显示这些信息，它也可以帮助其他人！请查看here!|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|149636|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/danmakenoise/link-status^0|U|B|1X|5|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

I see myself and others having this same question a lot. I wrote a small CLI for myself called <code>link-status</code> to display this info, and it may help others out too! Check it out <a href="https://github.com/danmakenoise/link-status" rel="nofollow noreferrer">here!</a>

blocks|key|151048|text|在Windows上，您只需查看目录：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|151049|C:\Users\[username]\AppData\Roaming\npm\node_modules|code-block|syntax|javascript|151050|您应该会看到在那里列出的任何符号链接库，以及安装的任何全局库。|151051|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|$]]

On Windows you can just look at the directory:
<pre class="lang-none prettyprint-override"><code>C:\Users\[username]\AppData\Roaming\npm\node_modules
</code></pre>
You should see any of the symbolic linked libraries listed there, along side any global library installs.

I am looking for a command that will list the names of global modules that I have <code>npm link</code>'d to local copies, also listing the local path.
In fact, a list of all globally installed modules would be even better, with the <code>npm link</code>'d ones flagged somehow.

How to list all the Node.js modules I have linked with npm

我正在寻找一个命令，它将列出我已经npm link'd到本地副本的全局模块的名称，也列出了本地路径。事实上，一份all全局安装模块的列表会更好，因为npm link'd ones 以某种方式标记了。

问如何列出我链接到npm的所有Node.js模块
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何列出我链接到npm的所有Node.js模块EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何列出我链接到npm的所有Node.js模块
EN