-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
migrate to mkdirp v1 #112
Comments
how about dropping it and use nodes built in mkdir (recursive option) instead? |
we have to support node 0.10.x - that said - neither of the above (built in mkdir or promises) can be merged in... is there a security issue here or just 'lets keep node modern' which is totally legit, just not with this lib unfortunately open to discussion if there is a reason outside of staying modern... |
it's rather 'lets not depend on deprecated things' |
... and use less dependencies and making it smaller |
I actually feel the same way and have opened an issue (that I need to clean up b/c it was a brain dump) #122 perhaps it should just say:
at least that's what I am trying to say, in a very round about way :) |
You should consider updating mkdirp at least to a version that fixes GHSA-xvch-5gv4-984h. See: isaacs/node-mkdirp#27 |
I'm not fully understanding the reasoning here but skimming through some older comments it seems to be related to embedded machines running older node versions? Correct me if I'm wrong though. My two cents about this is that some systems are using older nodejs versions and will not / cannot update but they would probably not update
|
mkdirp has a new 0.5.6 version with updated minimist dependency. It should fix the issue for now. |
npm says that mkdirp v0.x has been deprecated:
The text was updated successfully, but these errors were encountered: