fs-extra vs ncp vs copyfiles vs cpx vs copy-dir
File Copying Libraries in Node.js Comparison
1 Year
fs-extrancpcopyfilescpxcopy-dirSimilar Packages:
What's File Copying Libraries in Node.js?

These libraries provide various functionalities for copying files and directories in Node.js applications. They simplify the process of duplicating files and directories, allowing developers to manage file systems more efficiently. Each library has its unique features, performance characteristics, and use cases, making them suitable for different scenarios in web development.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
fs-extra107,163,0509,52555.3 kB15a month agoMIT
ncp3,639,167683-8110 years agoMIT
copyfiles1,295,388414-554 years agoMIT
cpx262,934527-358 years agoMIT
copy-dir87,533---5 years agoMIT
Feature Comparison: fs-extra vs ncp vs copyfiles vs cpx vs copy-dir

Basic Functionality

  • fs-extra:

    fs-extra extends the native fs module with additional methods such as copy, move, and remove, providing a comprehensive set of file manipulation capabilities. It supports recursive copying and ensures that all files and subdirectories are copied correctly.

  • ncp:

    ncp is a simple library that focuses on copying files and directories with progress reporting. It is designed to handle large directory structures efficiently while providing feedback on the copying process.

  • copyfiles:

    copyfiles allows for copying files and directories using glob patterns, enabling users to specify which files to copy based on their names or extensions. This flexibility makes it suitable for more complex copying tasks.

  • cpx:

    cpx not only copies files and directories but also offers a watch mode that automatically copies files when changes are detected. This feature is particularly useful during development for keeping build directories updated.

  • copy-dir:

    copy-dir provides a straightforward API for copying entire directories. It is designed for simplicity and does not include additional features, making it easy to integrate into projects that require basic directory copying.

Performance

  • fs-extra:

    fs-extra is highly optimized for performance and can handle large files and complex directory structures efficiently. Its recursive copy feature ensures that all files are copied without unnecessary overhead.

  • ncp:

    ncp is efficient for copying large directories and provides progress feedback, which can be useful for monitoring long-running copy operations. It is designed to handle large file structures without significant performance degradation.

  • copyfiles:

    copyfiles performs well for copying files based on glob patterns, but its performance may vary depending on the complexity of the patterns used. It is generally suitable for moderate file copying tasks.

  • cpx:

    cpx is designed for development environments where files change frequently. Its watch mode can introduce some overhead, but it is optimized for real-time copying, making it efficient for keeping directories in sync during development.

  • copy-dir:

    copy-dir is lightweight and optimized for basic directory copying tasks, making it fast for small to medium-sized directories. However, it does not handle large files or complex structures as efficiently as some other libraries.

Ease of Use

  • fs-extra:

    fs-extra provides a rich API that may require some learning but offers extensive functionality. Once familiar, developers can leverage its full capabilities for complex file operations.

  • ncp:

    ncp is straightforward to use, with a simple API for copying files and directories. Its progress reporting feature adds a layer of usability, making it easy to monitor operations.

  • copyfiles:

    copyfiles offers a command-line interface that simplifies usage for developers who prefer to work directly from the terminal. Its glob pattern support adds a layer of complexity but enhances flexibility.

  • cpx:

    cpx is user-friendly, especially for developers familiar with watching file changes. Its API is straightforward, and the watch mode is easy to enable, making it accessible for real-time file management.

  • copy-dir:

    copy-dir has a simple and intuitive API, making it easy for developers to use without extensive documentation. It is suitable for quick tasks where simplicity is key.

Additional Features

  • fs-extra:

    fs-extra includes a wide range of additional file manipulation methods beyond copying, such as moving and removing files. This versatility makes it a powerful tool for developers needing comprehensive file system utilities.

  • ncp:

    ncp provides progress reporting during file copying, which is beneficial for large operations. However, it does not include advanced features like file watching or glob pattern support.

  • copyfiles:

    copyfiles supports glob patterns and offers a command-line interface, making it versatile for various file copying scenarios. However, it lacks advanced features like progress reporting.

  • cpx:

    cpx includes a watch mode that automatically copies files when changes are detected, making it ideal for development environments. This feature sets it apart from simpler libraries that do not offer real-time synchronization.

  • copy-dir:

    copy-dir focuses solely on directory copying and does not include additional features such as progress reporting or file watching, making it suitable for basic use cases.

Community and Support

  • fs-extra:

    fs-extra has a large and active community, with extensive documentation and resources available. It is widely used and well-supported, making it a reliable choice for developers.

  • ncp:

    ncp has a smaller community, but it is still maintained and has adequate documentation. Users may find support through GitHub issues and community forums.

  • copyfiles:

    copyfiles has a moderate community presence, with sufficient documentation and examples available. However, it may not have as extensive support as larger libraries.

  • cpx:

    cpx has a growing community, and its watch feature is popular among developers. Documentation is available, but users may need to rely on community support for advanced use cases.

  • copy-dir:

    copy-dir has a smaller community compared to other libraries, which may result in limited support and fewer resources available for troubleshooting.

How to Choose: fs-extra vs ncp vs copyfiles vs cpx vs copy-dir
  • fs-extra:

    Use fs-extra if you need a comprehensive file system utility that extends the native fs module with additional methods. It provides a rich set of features, including recursive directory copying and file manipulation, making it suitable for complex file operations.

  • ncp:

    Choose ncp if you are looking for a simple and reliable way to copy files and directories with progress reporting. It is particularly useful for copying large directories while providing feedback on the copying process.

  • copyfiles:

    Select copyfiles if you require a versatile tool that supports glob patterns for selecting files and directories. It is particularly useful for copying specific files based on patterns and offers a command-line interface for convenience.

  • cpx:

    Opt for cpx if you need a tool that supports watching files and directories for changes, allowing for automatic copying during development. It is ideal for scenarios where you want to keep a destination folder in sync with source files.

  • copy-dir:

    Choose copy-dir if you need a simple and straightforward solution for copying directories without additional features. It is lightweight and easy to use for basic directory copying tasks.

README for fs-extra

Node.js: fs-extra

fs-extra adds file system methods that aren't included in the native fs module and adds promise support to the fs methods. It also uses graceful-fs to prevent EMFILE errors. It should be a drop in replacement for fs.

npm Package License build status downloads per month JavaScript Style Guide

Why?

I got tired of including mkdirp, rimraf, and ncp in most of my projects.

Installation

npm install fs-extra

Usage

CommonJS

fs-extra is a drop in replacement for native fs. All methods in fs are attached to fs-extra. All fs methods return promises if the callback isn't passed.

You don't ever need to include the original fs module again:

const fs = require('fs') // this is no longer necessary

you can now do this:

const fs = require('fs-extra')

or if you prefer to make it clear that you're using fs-extra and not fs, you may want to name your fs variable fse like so:

const fse = require('fs-extra')

you can also keep both, but it's redundant:

const fs = require('fs')
const fse = require('fs-extra')

ESM

There is also an fs-extra/esm import, that supports both default and named exports. However, note that fs methods are not included in fs-extra/esm; you still need to import fs and/or fs/promises seperately:

import { readFileSync } from 'fs'
import { readFile } from 'fs/promises'
import { outputFile, outputFileSync } from 'fs-extra/esm'

Default exports are supported:

import fs from 'fs'
import fse from 'fs-extra/esm'
// fse.readFileSync is not a function; must use fs.readFileSync

but you probably want to just use regular fs-extra instead of fs-extra/esm for default exports:

import fs from 'fs-extra'
// both fs and fs-extra methods are defined

Sync vs Async vs Async/Await

Most methods are async by default. All async methods will return a promise if the callback isn't passed.

Sync methods on the other hand will throw if an error occurs.

Also Async/Await will throw an error if one occurs.

Example:

const fs = require('fs-extra')

// Async with promises:
fs.copy('/tmp/myfile', '/tmp/mynewfile')
  .then(() => console.log('success!'))
  .catch(err => console.error(err))

// Async with callbacks:
fs.copy('/tmp/myfile', '/tmp/mynewfile', err => {
  if (err) return console.error(err)
  console.log('success!')
})

// Sync:
try {
  fs.copySync('/tmp/myfile', '/tmp/mynewfile')
  console.log('success!')
} catch (err) {
  console.error(err)
}

// Async/Await:
async function copyFiles () {
  try {
    await fs.copy('/tmp/myfile', '/tmp/mynewfile')
    console.log('success!')
  } catch (err) {
    console.error(err)
  }
}

copyFiles()

Methods

Async

Sync

NOTE: You can still use the native Node.js methods. They are promisified and copied over to fs-extra. See notes on fs.read(), fs.write(), & fs.writev()

What happened to walk() and walkSync()?

They were removed from fs-extra in v2.0.0. If you need the functionality, walk and walkSync are available as separate packages, klaw and klaw-sync.

Third Party

CLI

fse-cli allows you to run fs-extra from a console or from npm scripts.

TypeScript

If you like TypeScript, you can use fs-extra with it: https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/fs-extra

File / Directory Watching

If you want to watch for changes to files or directories, then you should use chokidar.

Obtain Filesystem (Devices, Partitions) Information

fs-filesystem allows you to read the state of the filesystem of the host on which it is run. It returns information about both the devices and the partitions (volumes) of the system.

Misc.

Hacking on fs-extra

Wanna hack on fs-extra? Great! Your help is needed! fs-extra is one of the most depended upon Node.js packages. This project uses JavaScript Standard Style - if the name or style choices bother you, you're gonna have to get over it :) If standard is good enough for npm, it's good enough for fs-extra.

js-standard-style

What's needed?

  • First, take a look at existing issues. Those are probably going to be where the priority lies.
  • More tests for edge cases. Specifically on different platforms. There can never be enough tests.
  • Improve test coverage.

Note: If you make any big changes, you should definitely file an issue for discussion first.

Running the Test Suite

fs-extra contains hundreds of tests.

  • npm run lint: runs the linter (standard)
  • npm run unit: runs the unit tests
  • npm run unit-esm: runs tests for fs-extra/esm exports
  • npm test: runs the linter and all tests

When running unit tests, set the environment variable CROSS_DEVICE_PATH to the absolute path of an empty directory on another device (like a thumb drive) to enable cross-device move tests.

Windows

If you run the tests on the Windows and receive a lot of symbolic link EPERM permission errors, it's because on Windows you need elevated privilege to create symbolic links. You can add this to your Windows's account by following the instructions here: http://superuser.com/questions/104845/permission-to-make-symbolic-links-in-windows-7 However, I didn't have much luck doing this.

Since I develop on Mac OS X, I use VMWare Fusion for Windows testing. I create a shared folder that I map to a drive on Windows. I open the Node.js command prompt and run as Administrator. I then map the network drive running the following command:

net use z: "\\vmware-host\Shared Folders"

I can then navigate to my fs-extra directory and run the tests.

Naming

I put a lot of thought into the naming of these functions. Inspired by @coolaj86's request. So he deserves much of the credit for raising the issue. See discussion(s) here:

  • https://github.com/jprichardson/node-fs-extra/issues/2
  • https://github.com/flatiron/utile/issues/11
  • https://github.com/ryanmcgrath/wrench-js/issues/29
  • https://github.com/substack/node-mkdirp/issues/17

First, I believe that in as many cases as possible, the Node.js naming schemes should be chosen. However, there are problems with the Node.js own naming schemes.

For example, fs.readFile() and fs.readdir(): the F is capitalized in File and the d is not capitalized in dir. Perhaps a bit pedantic, but they should still be consistent. Also, Node.js has chosen a lot of POSIX naming schemes, which I believe is great. See: fs.mkdir(), fs.rmdir(), fs.chown(), etc.

We have a dilemma though. How do you consistently name methods that perform the following POSIX commands: cp, cp -r, mkdir -p, and rm -rf?

My perspective: when in doubt, err on the side of simplicity. A directory is just a hierarchical grouping of directories and files. Consider that for a moment. So when you want to copy it or remove it, in most cases you'll want to copy or remove all of its contents. When you want to create a directory, if the directory that it's suppose to be contained in does not exist, then in most cases you'll want to create that too.

So, if you want to remove a file or a directory regardless of whether it has contents, just call fs.remove(path). If you want to copy a file or a directory whether it has contents, just call fs.copy(source, destination). If you want to create a directory regardless of whether its parent directories exist, just call fs.mkdirs(path) or fs.mkdirp(path).

Credit

fs-extra wouldn't be possible without using the modules from the following authors:

License

Licensed under MIT

Copyright (c) 2011-2024 JP Richardson