move-concurrently 1.0.1
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.
move-concurrently@1.0.1 was published on 2017-03-16. Its manifest declares 6 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
Deprecated: This package is no longer supported.
All move-concurrently versions · Permanent reference to 1.0.1 · Latest release
Package specifications
| Version | 1.0.1 |
|---|---|
| License declaration | ISC |
| Published | 2017-03-16T23:24:29.189Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 6 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | move.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 28 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install move-concurrently 1.0.1
npm install move-concurrently@1.0.1 pnpm add move-concurrently@1.0.1 yarn add move-concurrently@1.0.1
Runtime dependencies
- aproba ^1.1.1
- mkdirp ^0.5.1
- rimraf ^2.5.4
- run-queue ^1.0.3
- copy-concurrently ^1.0.0
- fs-write-stream-atomic ^1.0.8
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- aproba@1.2.0 — direct
- balanced-match@1.0.2 — indirect
- brace-expansion@1.1.21 — indirect
- concat-map@0.0.1 — indirect
- copy-concurrently@1.0.5 — direct
- core-util-is@1.0.3 — indirect
- fs-write-stream-atomic@1.0.10 — direct
- fs.realpath@1.0.0 — indirect
- glob@7.2.3 — indirect
- graceful-fs@4.2.11 — indirect
- iferr@0.1.5 — indirect
- imurmurhash@0.1.4 — indirect
- inflight@1.0.6 — indirect
- inherits@2.0.4 — indirect
- isarray@1.0.0 — indirect
- minimatch@3.1.5 — indirect
- minimist@1.2.8 — indirect
- mkdirp@0.5.6 — direct
- once@1.4.0 — indirect
- path-is-absolute@1.0.1 — indirect
- process-nextick-args@2.0.1 — indirect
- readable-stream@2.3.8 — indirect
- rimraf@2.7.1 — direct
- run-queue@1.0.3 — direct
- safe-buffer@5.1.2 — indirect
- string_decoder@1.1.1 — indirect
- util-deprecate@1.0.2 — indirect
- wrappy@1.0.2 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
Evidence and freshness
- https://registry.npmjs.org/move-concurrently/1.0.1 — retrieved 2026-10-29T07:21:11.193Z
- https://api.deps.dev/v3/systems/npm/packages/move-concurrently/versions/1.0.1 — retrieved 2026-10-29T07:21:11.709Z
- https://api.deps.dev/v3/systems/npm/packages/move-concurrently/versions/1.0.1:dependencies — retrieved 2026-10-29T07:21:11.757Z