Big update!Introducing GitHub Bot Commands. Learn more
Socket
Log inBook a demo

move-concurrently

Package Overview
Dependencies
6
Maintainers
1
Versions
2
Issues
File Explorer

Advanced tools

move-concurrently

Promises of moves of files or directories with rename, falling back to recursive rename/copy on EXDEV errors, with configurable concurrency and win32 junction support.

    1.0.1latest

Version published
Maintainers
1
Weekly downloads
7,640,450
decreased by-19.34%

Weekly downloads

Readme

Source

move-concurrently

Move files and directories.

const move = require('move-concurrently') move('/path/to/thing', '/new/path/thing').then(() => { // thing is now moved! }).catch(err => { // oh no! })

Uses rename to move things as fast as possible.

If you move across devices or on filesystems that don't support renaming large directories. That is, situations that result in rename returning the EXDEV error, then move will fallback to copy + delete.

When recursively copying directories it will first try to rename the contents before falling back to copying. While this will be slightly slower in true cross-device scenarios, it is MUCH faster in cases where the filesystem can't handle directory renames.

When copying ownership is maintained when running as root. Permissions are always maintained. On Windows, if symlinks are unavailable then junctions will be used.

INTERFACE

move(from, to, options) → Promise

Recursively moves from to to and resolves its promise when finished. If to already exists then the promise will be rejected with an EEXIST error.

Starts by trying to rename from to to.

Options are:

  • maxConcurrency – (Default: 1) The maximum number of concurrent copies to do at once.
  • isWindows - (Default: process.platform === 'win32') If true enables Windows symlink semantics. This requires an extra stat to determine if the destination of a symlink is a file or directory. If symlinking a directory fails then we'll try making a junction instead.

Options can also include dependency injection:

  • Promise - (Default: global.Promise) The promise implementation to use, defaults to Node's.
  • fs - (Default: require('fs')) The filesystem module to use. Can be used to use graceful-fs or to inject a mock.
  • writeStreamAtomic - (Default: require('fs-write-stream-atomic')) The implementation of writeStreamAtomic to use. Used to inject a mock.
  • getuid - (Default: process.getuid) A function that returns the current UID. Used to inject a mock.

Keywords

FAQs

What is move-concurrently?

Promises of moves of files or directories with rename, falling back to recursive rename/copy on EXDEV errors, with configurable concurrency and win32 junction support.

Is move-concurrently popular?

The npm package move-concurrently receives a total of 6,377,836 weekly downloads. As such, move-concurrently popularity was classified as popular.

Is move-concurrently well maintained?

We found that move-concurrently demonstrated a not healthy version release cadence and project activity because the last version was released a year ago.It has 1 open source maintainer collaborating on the project.

Last updated on 16 Mar 2017

Did you know?

Socket installs a Github app to automatically flag issues on every pull request and report the health of your dependencies. Find out what is inside your node modules and prevent malicious activity before you update the dependencies.

Install Socket
Socket

Product

Subscribe to our newsletter

Get open source security insights delivered straight into your inbox. Be the first to learn about new features and product updates.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc