fs-extra vs ncp vs copyfiles vs cpx vs copy-dir
File and Directory Copying Comparison
3 Years
fs-extrancpcopyfilescpxcopy-dirSimilar Packages:
What's File and Directory Copying?

File and Directory Copying libraries in Node.js provide developers with tools to copy files and directories programmatically. These libraries offer various features such as recursive copying, preserving file attributes, handling symbolic links, and providing progress callbacks. They are useful for tasks like building automation, file management, and creating deployment scripts. Each library has its own set of features, performance characteristics, and API designs, catering to different use cases and preferences.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
fs-extra105,279,468
9,58555.5 kB1713 days agoMIT
ncp3,672,361
684-8010 years agoMIT
copyfiles1,449,981
421-575 years agoMIT
cpx331,199
531-359 years agoMIT
copy-dir82,108
---5 years agoMIT
Feature Comparison: fs-extra vs ncp vs copyfiles vs cpx vs copy-dir

Recursive Copying

  • fs-extra:

    fs-extra offers robust recursive copying capabilities, including the ability to copy entire directories while preserving file attributes and structure.

  • ncp:

    ncp specializes in recursive copying, preserving file attributes, and handling symbolic links, making it efficient for comprehensive directory copying.

  • copyfiles:

    copyfiles supports recursive copying of files and directories using glob patterns, allowing for selective copying based on file matching.

  • cpx:

    cpx supports recursive copying of files and directories, with the added feature of watching for changes and copying incrementally.

  • copy-dir:

    copy-dir provides simple recursive copying of directories, making it easy to copy all contents without additional configuration.

File Attribute Preservation

  • fs-extra:

    fs-extra excels at preserving file attributes, including timestamps, permissions, and symbolic links, providing a more complete file copying solution.

  • ncp:

    ncp preserves file attributes, including timestamps and symbolic links, ensuring that the copied files maintain their original characteristics.

  • copyfiles:

    copyfiles does not focus on preserving file attributes; its primary feature is copying files based on glob patterns.

  • cpx:

    cpx preserves file attributes during copying, but its main focus is on watching files and copying them when changes occur.

  • copy-dir:

    copy-dir preserves basic file attributes during copying, but it does not explicitly handle symbolic links or advanced attributes.

Command-Line Interface (CLI)

  • fs-extra:

    fs-extra does not have a dedicated CLI, but it extends the fs module, allowing its methods to be used in any Node.js script.

  • ncp:

    ncp does not provide a CLI; it is designed to be used as a programmatic library within Node.js applications.

  • copyfiles:

    copyfiles offers a powerful CLI for copying files and directories, making it easy to integrate into build scripts and automation tasks.

  • cpx:

    cpx provides a simple CLI for copying files and directories, with options for watching and incremental copying, making it user-friendly for developers.

  • copy-dir:

    copy-dir does not provide a built-in CLI; it is primarily a programmatic library for use in Node.js applications.

Watching for Changes

  • fs-extra:

    fs-extra does not have built-in change-watching capabilities; it is focused on enhancing file system operations in Node.js.

  • ncp:

    ncp does not support watching for changes; it is designed for one-time recursive copying of files and directories.

  • copyfiles:

    copyfiles does not include change-watching features; it focuses on copying files based on specified patterns.

  • cpx:

    cpx includes built-in support for watching files and directories, automatically copying them when changes are detected, which is useful for development workflows.

  • copy-dir:

    copy-dir does not support watching for changes; it is a straightforward copying library without real-time capabilities.

Ease of Use: Code Examples

  • fs-extra:

    Comprehensive File Operations with fs-extra

    const fs = require('fs-extra');
    
    fs.copy('sourceDir', 'destDir', (err) => {
      if (err) throw err;
      console.log('Directory copied with attributes!');
    });
    
  • ncp:

    Simple Recursive Copying with ncp

    const ncp = require('ncp').ncp;
    
    ncp('sourceDir', 'destDir', (err) => {
      if (err) return console.error(err);
      console.log('Directory copied successfully!');
    });
    
  • copyfiles:

    File Copying with Glob Patterns using copyfiles

    const copyfiles = require('copyfiles');
    
    copyfiles(['src/*.js', 'src/styles/*.css'], 'dist', (err) => {
      if (err) throw err;
      console.log('Files copied successfully!');
    });
    
  • cpx:

    Incremental Copying with Change Watching using cpx

    const cpx = require('cpx');
    
    cpx.copy('src/**/*', 'dest', { watch: true }, () => {
      console.log('Files copied and watching for changes!');
    });
    
  • copy-dir:

    Simple Directory Copying with copy-dir

    const copyDir = require('copy-dir');
    
    copyDir('sourceDir', 'destDir', (err) => {
      if (err) throw err;
      console.log('Directory copied successfully!');
    });
    
How to Choose: fs-extra vs ncp vs copyfiles vs cpx vs copy-dir
  • fs-extra:

    Choose fs-extra if you need a comprehensive file system library that extends the built-in fs module with additional features like recursive directory copying, file moving, and more. It is suitable for projects that require robust file system operations beyond just copying.

  • ncp:

    Select ncp if you need a simple and efficient solution for recursively copying files and directories, especially if you want to preserve file attributes and handle symbolic links. It is lightweight and easy to use for quick copying tasks.

  • copyfiles:

    Select copyfiles if you require a command-line tool for copying files and directories with support for glob patterns, including the ability to create target directories automatically. It is great for build scripts and automation tasks.

  • cpx:

    Opt for cpx if you want a tool that supports one-way file and directory copying with built-in support for watching files and incremental copying. It is useful for development workflows where you need to keep directories in sync.

  • copy-dir:

    Choose copy-dir if you need a simple and lightweight solution for recursively copying directories with minimal configuration. It is ideal for straightforward copying tasks without additional dependencies.

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')

NOTE: The deprecated constants fs.F_OK, fs.R_OK, fs.W_OK, & fs.X_OK are not exported on Node.js v24.0.0+; please use their fs.constants equivalents.

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