"Fossies" - the Fresh Open Source Software Archive

Member "Atom/resources/app/apm/node_modules/ncp/README.md" (17 Oct 2016, 2491 Bytes) of archive /windows/misc/atom-windows.zip:

As a special service "Fossies" has tried to format the requested source page into HTML format (assuming markdown format). Alternatively you can here view or download the uninterpreted source code file. A member file download can also be achieved by clicking within a package contents listing on the according byte size field.

ncp - Asynchronous recursive file & directory copying

Build Status

Think cp -r, but pure node, and asynchronous. ncp can be used both as a CLI tool and programmatically.

Command Line usage

Usage is simple: ncp [source] [dest] [--limit=concurrency limit] [--filter=filter] --stopOnErr

The ‘filter’ is a Regular Expression - matched files will be copied.

The ‘concurrency limit’ is an integer that represents how many pending file system requests ncp has at a time.

‘stoponerr’ is a boolean flag that will tell ncp to stop immediately if any errors arise, rather than attempting to continue while logging errors. The default behavior is to complete as many copies as possible, logging errors along the way.

If there are no errors, ncp will output done. when complete. If there are errors, the error messages will be logged to stdout and to ./ncp-debug.log, and the copy operation will attempt to continue.

Programmatic usage

Programmatic usage of ncp is just as simple. The only argument to the completion callback is a possible error.

```javascript var ncp = require(‘ncp’).ncp;

ncp.limit = 16;

ncp(source, destination, function (err) { if (err) { return console.error(err); } console.log(‘done!’); }); ```

You can also call ncp like ncp(source, destination, options, callback). options should be a dictionary. Currently, such options are available:

Please open an issue if any bugs arise. As always, I accept (working) pull requests, and refunds are available at /dev/null.