All Versions
88
Latest Version
Avg Release Cycle
80 days
Latest Release
172 days ago

Changelog History
Page 2

  • v6.0.0 Changes

    May 01, 2018
    • โฌ‡๏ธ Drop support for Node.js versions 4, 5, & 7 (#564)
    • ๐Ÿšš Rewrite move to use fs.rename where possible (#549)
    • Don't convert relative paths to absolute paths for filter (#554)
    • ๐Ÿ“„ copy*'s behavior when preserveTimestamps is false has been OS-dependent since 5.0.0, but that's now explicitly noted in the docs (#563)
    • ๐Ÿšš Fix subdirectory detection for copy* & move* (#541)
    • ๐Ÿ– Handle case-insensitive paths correctly in copy* (#568)
  • v5.0.0 Changes

    December 11, 2017

    ๐Ÿš€ Significant refactor of copy() & copySync(), including breaking changes. No changes to other functions in this release.

    Huge thanks to @manidlou for doing most of the work on this release.

    • ๐Ÿ—„ The filter option can no longer be a RegExp (must be a function). This was deprecated since fs-extra v1.0.0. #512
    • copy()'s filter option can now be a function that returns a Promise. #518
    • ๐Ÿ‘ copy() & copySync() now use fs.copyFile()/fs.copyFileSync() in environments that support it (currently Node 8.5.0+). Older Node versions still get the old implementation. #505
    • Don't allow copying a directory into itself. #83
    • ๐Ÿ– Handle copying between identical files. #198
    • Error out when copying an empty folder to a path that already exists. #464
    • Don't create dest's parent if the filter function aborts the copy() operation. #517
    • ๐Ÿ›  Fix writeStream not being closed if there was an error in copy(). #516
  • v4.0.3 Changes

    December 05, 2017
    • ๐Ÿ›  Fix wrong chmod values in fs.remove() #501
    • ๐Ÿ›  Fix TypeError on systems that don't have some fs operations like lchown #520
  • v4.0.2 Changes

    September 12, 2017
    • Added EOL option to writeJson* & outputJson* (via upgrade to jsonfile v4)
    • Added promise support to fs.copyFile() in Node 8.5+
    • โž• Added .js extension to main field in package.json for better tooling compatibility. #485
  • v4.0.1 Changes

    July 31, 2017

    ๐Ÿ›  Fixed

    • Previously, ensureFile() & ensureFileSync() would do nothing if the path was a directory. Now, they error out for consistency with ensureDir(). #465, #466, #470
  • v4.0.0 Changes

    July 14, 2017

    ๐Ÿ”„ Changed

    • ๐Ÿ’ฅ BREAKING: The promisified versions of fs.read() & fs.write() now return objects. See [the docs](docs/fs-read-write.md) for details. #436, #449
    • ๐Ÿšš fs.move() now errors out when destination is a subdirectory of source. #458
    • ๐Ÿšš Applied upstream fixes from rimraf to fs.remove() & fs.removeSync(). #459

    ๐Ÿ›  Fixed

    • โ™ป๏ธ Got fs.outputJSONSync() working again; it was broken due to refactoring. #428

    ๐Ÿ“„ Also clarified the docs in a few places.

  • v3.0.1 Changes

    May 04, 2017
    • ๐Ÿ›  Fix bug in move() & moveSync() when source and destination are the same, and source does not exist. #415
  • v3.0.0 Changes

    April 27, 2017

    โž• Added

    • ๐Ÿ’ฅ BREAKING: Added Promise support. All asynchronous native fs methods and fs-extra methods now return a promise if the callback is not passed. #403
    • ๐Ÿ—„ pathExists(), a replacement for the deprecated fs.exists. pathExists has a normal error-first callback signature. Also added pathExistsSync, an alias to fs.existsSync, for completeness. #406

    โœ‚ Removed

    • ๐Ÿ’ฅ BREAKING: Removed support for setting the default spaces for writeJson(), writeJsonSync(), outputJson(), & outputJsonSync(). This was undocumented. #402

    ๐Ÿ”„ Changed

    • โฌ†๏ธ Upgraded jsonfile dependency to v3.0.0:
      • BREAKING: Changed behavior of throws option for readJsonSync(); now does not throw filesystem errors when throws is false.
    • ๐Ÿ’ฅ BREAKING: writeJson(), writeJsonSync(), outputJson(), & outputJsonSync() now output minified JSON by default for consistency with JSON.stringify(); set the spaces option to 2 to override this new behavior. #402
    • ๐Ÿ‘‰ Use Buffer.allocUnsafe() instead of new Buffer() in environments that support it. #394

    ๐Ÿ›  Fixed

    • ๐Ÿ removeSync() silently failed on Windows in some cases. Now throws an EBUSY error. #408
  • v2.1.2 Changes

    March 16, 2017

    ๐Ÿ›  Fixed

    • ๐Ÿ Weird windows bug that resulted in ensureDir()'s callback being called twice in some cases. This bug may have also affected remove(). See #392, #393
  • v2.1.1 Changes

    March 15, 2017

    ๐Ÿ›  Fixed

    • โช Reverted 5597bd, this broke compatibility with Node.js versions v4+ but less than v4.5.0.
    • โœ‚ Remove Buffer.alloc() usage in moveSync().