copy/copySync meta issue

@manidlou I think you mentioned copySync still needs updated to match the changes you made to copy in develop. Is that correct? What else needs done before releasing the work done on develop?

Just FYI, I’m planning on releasing a major version with just the changes in copy/copySync; that way if there’s regressions, we can simply tell people not to upgrade until we get things fixed.

---

Edit: Tasklist:

• copySync needs updated to match copy
  • Remove recursive option
  • Fix #83
  • Fix #198
  • Fix #464
• Port #511 to develop

[RyanZim]

Also noting https://github.com/jprichardson/node-fs-extra/pull/511 needs ported.

I’m starting a tasklist in the OP; @manidlou please check off items that are merged to develop.

[manidlou]

That’s correct @RyanZim. In terms of changes for copySync, these are the things that I think need to be changed or fixed:

• There is a recursive option that was never been documented, which I think needs to be removed as it directly affects the copySync behavior for symlinks (src). Related issue: #447.
• copySync currently fails for the old and infamous issues of #83 and #198 as well as #464.
• I also like to test if we get a better perf by using recursive pattern instead of Array.forEach when copying directories.

I do my best to complete them as fast as possible!

I’m planning on releasing a major version with just the changes in copy/copySync; that way if there’s regressions, we can simply tell people not to upgrade until we get things fixed.

Sounds good! 👍