* BREAKING: Drop old Node support, require v10+
Update CI configs
* Remove references and test fencing for old Node versions
* Use object spread properties
* Use octal literal notation
* Use optional catch bindings
* Remove secure-random from dev-deps (#610)
* fix ensureDir() doc
* moveSync: refactor to use renameSync
* copy*(): fix copying bind-mounted directories (#618)
* copy*(): fix copying bind-mounted dirs
* copy*(): fix case-insensitive-paths tests
* copy*(): refactor to check paths more efficiently
* destructure stats object after checking err
* move*(): check paths before moving
* move*(): add case-insensitive paths test
* remove unnecessary done callback from test
* copy*(): add new option checkPathsBeforeCopying
* update copy*() docs to include checkPathsBeforeCopying
* some reformatting
* copy*(): use fs.stat with bigint option
* move*(): refactor to use the internal stat functions
* move*(): add test for prevent moving identical
* disable graceful-fs in copy and move tests
* fix parsing node version
* tiny reformat
* update copy*() docs
* refactor parsing node version
* use semver to parse node version in tests
After looking at rimraf, I began to fear that node-fs-extra, which
is based on rimraf, might also automatically glob things. I find
this confusing when the API is being used as an overlay of the
node built-in fs module which never expands globs. This test
explicitly verifies that the remove() function does not follow
glob characters.
We aren't using rimraf's glob support, and glob is a rather large
dependency.
Changes:
- Remove glob support from rimraf
- Remove move()'s dependency on rimraf; use fs-extra.remove instead
- Make rimraf a devDependency; it is used in the tests
