Update fs-extra to version 2.1.1 🚀 #59
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hefangshi
force-pushed
the
greenkeeper-fs-extra-2.1.1
branch
from
39f007d
to
8e5c276
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
fs-extra just published its new version 2.1.1.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of fs-extra.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 413 commits .
cfcf3132.1.1659fafaUpdate CHANGELOGb121cf0Use new Buffer() in moveSync() to support full Node.js v4 linee02c07bRevert "Use Buffer.alloc() instead of deprecated new Buffer() in copy-file-sync, add engines field to package.json to specify min node v4.5.0"90b36092.1.06ebcb9cUpdate CHANGELOGefe0d80Merge pull request #378 from jdalton/move-check8d978dbDon't move when source and dest paths are the same.cf2c50dMerge pull request #386 from jprichardson/changelog4db96c5Update CHANGELOG1f30161Merge pull request #384 from jprichardson/docs-cleanup-async-methods83a6190docs: Refactor remove exmaple to use remove instead of removeSync936011edocs: Refactor remove and removeSync parameter namefc5fca9docs: Refactor docs to include parameters typee46b820Merge pull request #383 from jprichardson/docs-refactor-readJson-exampleThere are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.