Update dependency fs-extra to v10 #192
Open
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.
This PR contains the following updates:
0.30.0->10.0.1Release Notes
jprichardson/node-fs-extra
v10.0.1Compare Source
sideEffects: falsetopackage.json(#941)v10.0.0Compare Source
Breaking changes
The following changes, although technically semver-major, will not affect the vast majority of users:
ensureLink*()/ensureSymlink*()(#826, #786, #870)copy*()unknown file type (#880)remove*()(#882)Improvements
move*(), even on technically case-insensitive filesystems (#759, #801)fs.rm*()forremove*()in environments that support it (#882, #806)emptyDir()performance (#885)Bugfixes
copy*()'sfilterfunction is not called more than necessary (#883, #809)move*()raisingEPERMerror when moving a file to the root of a drive on Windows (#897, #819)Miscellaneous changes
at-least-nodeas a dependency (#896)v9.1.0Compare Source
fs.rm()(#841, #860)v9.0.1Compare Source
ensureFile()when used with Jest on Windows (#804, #805)process.umask()call (#791)v9.0.0Compare Source
Breaking changes
ensureDir*to use a fork of https://github.com/sindresorhus/make-dir to make use of native recursivefs.mkdirwhere possible (#619, #756)atimeforcopy*withpreserveTimestampsoption (#633)The following changes, allthough technically breaking, will not affect the vast majority of users:
outputJsonnow outputs objects as they were when the function was called, even if they are mutated later (#702, #768)nullas an options parameter to*Json*methods (#745, #768)Improvements
fs.writev&fs.opendir(#747)ensureFile(#696, #744)Miscellaneous changes
universalifydependency (#767)v8.1.0Compare Source
fs.realpath.nativein Node v9.2+ (#650, #682)graceful-fsdependency (#700)graceful-fseverywhere (#700)v8.0.1Compare Source
Maximum call stack size exceedederror inutil/stat(#679)v8.0.0Compare Source
NOTE: Node.js v6 support is deprecated, and will be dropped in the next major release.
renameSync()under the hood inmoveSync()copy*()(#613, #618)move()with case-insensitive file systemsfs.stat()'sbigintoption incopy*()&move*()where possible (#657)v7.0.1Compare Source
removeSync()on Windows, in some cases, it would error out withENOTEMPTY(#646)modeoption forensureDir*()(#587)v7.0.0Compare Source
copy*()handling of symlinks to properly detect symlinks that point to the same file. (#582)fs.lchmod()(#596)enginesfield topackage.json(#580)v6.0.1Compare Source
fs.promisesExperimentalWarningon Node v10.1.0 (#578)v6.0.0Compare Source
moveto usefs.renamewhere possible (#549)filter(#554)copy*'s behavior whenpreserveTimestampsisfalsehas been OS-dependent since 5.0.0, but that's now explicitly noted in the docs (#563)copy*&move*(#541)copy*(#568)v5.0.0Compare Source
Significant refactor of
copy()©Sync(), including breaking changes. No changes to other functions in this release.Huge thanks to @manidlou for doing most of the work on this release.
filteroption can no longer be a RegExp (must be a function). This was deprecated since fs-extra v1.0.0. #512copy()'sfilteroption can now be a function that returns a Promise. #518copy()©Sync()now usefs.copyFile()/fs.copyFileSync()in environments that support it (currently Node 8.5.0+). Older Node versions still get the old implementation. #505dest's parent if thefilterfunction aborts thecopy()operation. #517writeStreamnot being closed if there was an error incopy(). #516v4.0.3Compare Source
chmodvalues infs.remove()#501TypeErroron systems that don't have somefsoperations likelchown#520v4.0.2Compare Source
EOLoption towriteJson*&outputJson*(via upgrade to jsonfile v4)fs.copyFile()in Node 8.5+.jsextension tomainfield inpackage.jsonfor better tooling compatibility. #485v4.0.1Compare Source
Fixed
ensureFile()&ensureFileSync()would do nothing if the path was a directory. Now, they error out for consistency withensureDir(). #465, #466, #470v4.0.0Compare Source
Changed
fs.read()&fs.write()now return objects. See the docs for details. #436, #449fs.move()now errors out when destination is a subdirectory of source. #458rimraftofs.remove()&fs.removeSync(). #459Fixed
fs.outputJSONSync()working again; it was broken due to refactoring. #428Also clarified the docs in a few places.
v3.0.1Compare Source
move()&moveSync()when source and destination are the same, and source does not exist. #415v3.0.0Compare Source
Added
pathExists(), a replacement for the deprecatedfs.exists.pathExistshas a normal error-first callback signature. Also addedpathExistsSync, an alias tofs.existsSync, for completeness. #406Removed
writeJson(),writeJsonSync(),outputJson(), &outputJsonSync(). This was undocumented. #402Changed
throwsoption forreadJsonSync(); now does not throw filesystem errors whenthrowsisfalse.writeJson(),writeJsonSync(),outputJson(), &outputJsonSync()now output minified JSON by default for consistency withJSON.stringify(); set thespacesoption to2to override this new behavior. #402Buffer.allocUnsafe()instead ofnew Buffer()in environments that support it. #394Fixed
removeSync()silently failed on Windows in some cases. Now throws anEBUSYerror. #408v2.1.2Compare Source
Fixed
ensureDir()'s callback being called twice in some cases. This bug may have also affectedremove(). See #392, #393v2.1.1Compare Source
Fixed
5597bd, this broke compatibility with Node.js versions v4+ but less thanv4.5.0.Buffer.alloc()usage inmoveSync().v2.1.0Compare Source
Thanks to Mani Maghsoudlou (@manidlou) & Jan Peer Stöcklmair (@JPeer264) for their extraordinary help with this release!
Added
moveSync()See [#309], #381. (@manidlou)copy()andcopySync()'sfilteroption now gets the destination path passed as the second parameter. #366 (@manidlou)Changed
Buffer.alloc()instead of deprecatednew Buffer()incopySync(). #380 (@manidlou)Fixed
move()shouldn't error out when source and dest are the same. #377, #378 (@jdalton)v2.0.0Compare Source
Removed
v0.12. The Node foundation stopped officially supporting iton Jan 1st, 2017.
walk()andwalkSync().walkSync()was only part offs-extrafor a littleover two months. Use klaw instead of
walk(), in fact,walk()was justan alias to klaw. For
walkSync()use klaw-sync. See: [#338], [#339]Changed
clobbertooverwrite. This affectscopy(),copySync(), andmove(). [#330], [#333]docs/. [#340]Fixed
copySync()like incopy(). [#324]copy()can fail. [#326]v1.0.0Compare Source
After five years of development, we finally have reach the 1.0.0 milestone! Big thanks goes
to Ryan Zim for leading the charge on this release!
Added
walkSync()Changed
rimafglobbing, wasn't used. [#280]copy()/copySync()optionfilterif it's aRegExp.filtershould now be a function.rimraf. This is temporary and was done becauserimrafdepended upon the beefyglobwhichfs-extradoes not use. [#300]Fixed
utimesMillis()[#271]copySync()failed if user didn't own file. [#199], [#301]Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.