-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump major version of glob #2247
Comments
See
|
npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree. |
I can see this is done by c9bcfc1 but still need them to actually cut a release |
That and still it's only v3. @boneskull I feel this is rather urgent. Can you cut a release from this? |
@eljefedelrodeodeljefe What's urgent about it? |
(a release won't happen until #2231 is merged; this will likely happen before Node.js v7 is released. if you're in a hurry, you can either suppress the warnings or |
It's very bad UX for two thirds of npm users seeing deprecations warnings and wondering what is wrong and not being able to do anything. |
hmm. Waiting for that PR seems ambitious. |
channeling Allen Iverson I mean, listen, we're sitting here talking about a warning. Not an error. Not an error. Not an error. But we're talking about a warning. We're not talking about an error. We're not actually talking about an error, where it actually matters, but we're talking about a warning. I've seen maybe 10 issues created for this warning. I am not sure what is so scary about a warning involving a version of Node.js that is not released yet. Let's just all take a deep breath and realize that the sky will not fall. We'll do the next release methodically to mitigate the likelihood of actual errors. We're not going to rush it to suppress a warning. |
Yeah that's all fine. Still that makes me question why an integral part of the ecosystem fails to nurture its development by not updating ancient dependencies. The is the pre-stage of issues like left-pad and deeply worry me. |
It's pretty obvious at this point that @boneskull
He's described a workaround, I just updated to use it and moved on. Here are the docs for anyone not familiar with that - ironically using mocha as an example. Comparing this to left-pad is a bit poor though. The team here deserves a bit of gratitude for the work being put in. |
Can you please bump the version of glob? I think this repo is the reason why I see deprecations warnings for
graceful-fs
on nearly everynpm install
The text was updated successfully, but these errors were encountered: