-
Notifications
You must be signed in to change notification settings - Fork 48
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
chore: add support for v0.11+ #81
Conversation
9e18aba
to
3bb7cbf
Compare
Current coverage is 89.28% (diff: 100%)@@ master #81 diff @@
==========================================
Files 2 2
Lines 26 28 +2
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
+ Hits 23 25 +2
Misses 3 3
Partials 0 0
|
3bb7cbf
to
57d22f7
Compare
import objAssign from 'es6-object-assign'; | ||
objAssign.polyfill(); // modifies the global object | ||
|
||
const pathExistsSync = (filePath) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know it's a tiny amount of code, but Sindre did write path-exists
for this. If nothing else, it is one less utility for us to manage.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We were originally using that, but it only works on node v4+ so I had to switch to a different implementation. This is based off this comment on a thread regarding the deprecation.
Weird, travis couldn't find commits for 2 jobs and one test timed out. I've restarted them, we'll see what happens. |
LGTM! |
I don't think this is too much of a maintenance burden, and it lets us take advantage of shx from within shelljs, which I think is a big win.
If I missed anything, let me know.
This blocks shelljs/shelljs#525