[BREAKING] moveSync: refactor to use renameSync#609
Conversation
|
I changed the base to |
JPeer264
left a comment
There was a problem hiding this comment.
Could not think of any addition. Also nice cleanups in the tests 👏
|
This will need rebased to fix merge conflicts. @manidlou you've been very helpful here at fs-extra, and too often, I feel like I'm the bottleneck with the release process. As a result, I've added you to fs-extra on npm (i.e. you now have |
|
@RyanZim thanks a lot for giving me publish rights. I am truly honored to be part of You are right about the conflict. I'll rebase this. |
3d9e8ac to
95a9c72
Compare
|
Rebased! |
|
@manidlou Sorry, seems npm was a little buggy and didn't give you access when I requested it. Now fixed; you should have access. |
|
Thanks @RyanZim I appreciate it! |
|
@jprichardson are you ok with this?! So that I can merge this since |
|
@manidlou yep, I'm okay with it |
fix #608.
Refactored
moveSyncto be consistent withmove. Also removed unnecessaryrimrafpackage from dev-deps.