entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://github.blog/2021-02-02-npm-7-is-now-generally-available/#peer-dependencies|blocks|key|adebl|text|我在尝试使用npmv7将v1锁文件更新为v2时遇到了同样的问题，就像你的代码库中的情况一样，唯一可行的方法是删除锁文件，清除缓存，并使用--+npm+i+-dedupe标志再次执行一次删除。重新构建包锁后，不带标志的npm+i再次工作，npm+ci也是如此。|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|4lipg|在此之前，我尝试了npm+i+--legacy-peer-deps，因为它似乎模仿npm+v6没有安装对等依赖项，但它也失败了，但是我认为有趣的是这个标志的存在，请查看npm+7公告页面以获得更多线索：https://github.blog/2021-02-02-npm-7-is-now-generally-available/#peer-dependencies|1fmp1|TLDR|4fs24|rm+package-lock.json
npm+cache+clear+--force
npm+i+--prefer-dedupe|code-block|syntax|javascript|8khgt^0|1Z|5|30|5|3A|6|0|9|O|2T|2A|0|0|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|W|G|@$H|X|I|Y|J|K]|$H|Z|I|10|J|K]|$H|11|I|12|J|K]]|L|@]|6|$]]|$A|M|C|N|2|E|F|13|G|@$H|14|I|15|J|K]]|L|@$H|16|I|17|A|18]]|6|$]]|$A|O|C|P|2|E|F|19|G|@]|L|@]|6|$]]|$A|Q|C|R|2|S|F|1A|G|@]|L|@]|6|$T|U]]|$A|V|C|-4|2|E|F|1B|G|@]|L|@]|6|$]]]]

I had the same issue when trying to update a v1 lockfile to v2 with npmv7, as it seems to be the case in your codebase, and the only way to make it work was to delete the lockfile, clear the cache and do a <code>npm i</code> again with the --prefer-dedupe flag.
With the package-lock rebuilt, <code>npm i</code> with no flag worked again, as did <code>npm ci</code>.
Before that, I tried <code>npm i --legacy-peer-deps</code> as it seemed to mimic npm v6 not installing peer dependencies and it failed too, however I think it's interesting to know this flag exists, check out the npm 7 announcement page for more clues : <a href="https://github.blog/2021-02-02-npm-7-is-now-generally-available/#peer-dependencies" rel="nofollow noreferrer">https://github.blog/2021-02-02-npm-7-is-now-generally-available/#peer-dependencies</a>
TLDR
<pre><code>rm package-lock.json
npm cache clear --force
npm i --prefer-dedupe
</code></pre>

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://github.com/npm/arborist/issues/330#issuecomment-947803995|blocks|key|4kjui|text|npm+update+&&+npm+i为我工作。|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|538sc|来源：https://github.com/npm/arborist/issues/330#issuecomment-947803995|cupc3^0|0|J|0|3|1T|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|P|G|@$H|Q|I|R|J|K]]|L|@]|6|$]]|$A|M|C|N|2|E|F|S|G|@]|L|@$H|T|I|U|A|V]]|6|$]]|$A|O|C|-4|2|E|F|W|G|@]|L|@]|6|$]]]]

<code>npm update &amp;&amp; npm i</code> works for me.
Source: <a href="https://github.com/npm/arborist/issues/330#issuecomment-947803995" rel="nofollow noreferrer">https://github.com/npm/arborist/issues/330#issuecomment-947803995</a>

entityMap|blocks|key|3a2ot|text|问题出在节点版本上，在将节点版本降级到v14.17.6之后，它工作得很好|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|el4ht^0|J|8|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@$A|I|B|J|C|D]]|E|@]|F|$]]|$2|G|4|-4|6|7|8|K|9|@]|E|@]|F|$]]]]

The problem was with node version, it works nicely after downgrading node version to <code>v14.17.6</code>

Every time I try to install packages using <code>npm install</code>, I'm getting <code>npm ERR! Tracker &quot;idealTree:inflate:&quot; already exists</code> error.
I've tried removing <code>node_modules</code> and clearing cache, but no luck for me.

npm ERR! Tracker "idealTree:inflate:" already exists

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

 每次我尝试使用npm install安装软件包时，都会遇到npm ERR! Tracker "idealTree:inflate:" already exists错误。 我尝试过删除node_modules和清除缓存，但没有成功。 

问npm错误！跟踪器"idealTree:inflate:“已经存在
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问npm错误！跟踪器"idealTree:inflate:“已经存在EN