Source: node-move-concurrently
Section: javascript
Priority: optional
Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org>
Uploaders: Pirate Praveen <praveen@debian.org>
Build-Depends:
 debhelper (>= 11~)
 , nodejs (>= 8~)
 , node-tap <!nocheck>
 , node-tacks <!nocheck>
 , node-run-queue (>= 1.0.3) <!nocheck>
 , node-rimraf (>= 2.5.4) <!nocheck>
 , node-fs-write-stream-atomic (>= 1.0.8) <!nocheck>
 , node-aproba (>= 1.1.1) <!nocheck>
 , node-mkdirp (>= 0.5.1) <!nocheck>
 , node-copy-concurrently (>= 1.0.0) <!nocheck>
Standards-Version: 4.2.1
Homepage: https://www.npmjs.com/package/move-concurrently
Vcs-Git: https://salsa.debian.org/js-team/node-move-concurrently.git
Vcs-Browser: https://salsa.debian.org/js-team/node-move-concurrently

Package: node-move-concurrently
Architecture: all
Depends:
 ${misc:Depends}
 , nodejs (>= 8~)
 , node-run-queue (>= 1.0.3)
 , node-rimraf (>= 2.5.4)
 , node-fs-write-stream-atomic (>= 1.0.8)
 , node-aproba (>= 1.1.1)
 , node-mkdirp (>= 0.5.1)
 , node-copy-concurrently (>= 1.0.0)
Description: Move files and directories 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.
 .
 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.
 .
 Node.js is an event-based server-side JavaScript engine.