npm WARN弃用graceful-fs@3.0.8:graceful-fs版本3 [英] npm WARN deprecated graceful-fs@3.0.8: graceful-fs version 3

查看:265
本文介绍了npm WARN弃用graceful-fs@3.0.8:graceful-fs版本3的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在运行npm install但是它给了我一个错误。我还尝试在更新之前运行以下命令。 $ npm install npm,我也更新了graceful-fs。

I am running npm install but it's giving me an error. I also tried to run below command before update. $npm install npm and also I updated graceful-fs.

$ npm install -g graceful-fs
graceful-fs@4.1.3 C:\Users\RDY672\AppData\Roaming\npm\node_modules\graceful-fs

错误如下:

$ npm install -g bower@1.3.12
npm WARN deprecated graceful-fs@3.0.8: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
npm WARN deprecated graceful-fs@2.0.3: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
npm ERR! cb() never called!
npm ERR! not ok code 0


推荐答案

TL; DR: 如果需要,只需提交错误,并暂时忽略弃用警告。除非它抛出错误,否则不是你的问题。

TL;DR: Just file bugs if necessary, and ignore the deprecation warnings for now. Unless it's throwing errors, it's not your problem.

最有可能的是,它间接取决于过时的版本offulful-fs取决于Node的内部模块(即使它不应该)。该模块必然确实在很大程度上依赖于Node的实现细节,但4.x在这方面写得不那么脆弱。在3.x和4.x之间的API中几乎没有什么变化。

Most likely, it's indirectly depending on an out-of-date version of graceful-fs that depends on Node's internal modules (even though it shouldn't). That module by necessity does depend heavily on Node's implementation details, but 4.x was written to be less brittle in that respect. Few things changed in the API between 3.x and 4.x.

对于它的价值而言,几周之前的一个计数使该模块成为第十个下载最多的模块NPM。我没有看到变化太大。并且由于该模块的大量使用份额(npm本身间接取决于过时的版本), Node已经设置了一个临时修复,他们试图让人们离开内部模块

For what it's worth, one count a couple weeks ago had that module as the tenth most downloaded on npm. I don't see that changing much. And because of the large use share of that module (npm itself indirectly depends on an outdated version), Node has already instated a temporary fix where they're trying to get people off of the internal modules.

所以不要担心除非你得到源自它的错误。我通常会忽略那些弃用警告,因为它们已经非常有名。

So don't worry unless you get errors originating from it. I generally ignore those deprecation warnings, as they're already very well known.

这篇关于npm WARN弃用graceful-fs@3.0.8:graceful-fs版本3的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆