Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
fs-extra contains methods that aren't included in the vanilla Node.js fs package. Such as mkdir -p, cp -r, and rm -rf.
The fs-extra package is a file system module for Node.js that extends the built-in 'fs' module. It provides additional methods and simplifies certain file operations, such as copying, moving, deleting files and directories, and more. It also adds promise support to the fs methods.
Copying files and directories
This feature allows you to copy files and directories from one location to another. The method returns a promise that resolves when the operation is complete.
const fs = require('fs-extra');
fs.copy('/path/to/source', '/path/to/dest')
.then(() => console.log('Copy successful!'))
.catch(err => console.error(err));
Moving files and directories
This feature enables you to move files and directories to a new location. Like copy, it returns a promise and provides a simple API for a task that would otherwise require multiple steps.
const fs = require('fs-extra');
fs.move('/path/to/source', '/path/to/dest')
.then(() => console.log('Move successful!'))
.catch(err => console.error(err));
Removing files and directories
This feature is used to delete files and directories. It is a safer and more powerful alternative to the standard 'fs.unlink' and 'fs.rmdir' methods, as it can remove non-empty directories.
const fs = require('fs-extra');
fs.remove('/path/to/dir')
.then(() => console.log('Removal successful!'))
.catch(err => console.error(err));
Reading and writing JSON files
This feature simplifies the process of reading and writing JSON files. It automatically handles stringifying objects when writing and parsing JSON data when reading.
const fs = require('fs-extra');
const myData = { name: 'fs-extra' };
fs.writeJson('/path/to/file.json', myData)
.then(() => console.log('Write successful!'))
.catch(err => console.error(err));
Ensuring a file or directory exists
This feature checks if a file or directory exists, and if it does not, it is created. This is useful for making sure that a given file or directory is present before performing operations on it.
const fs = require('fs-extra');
fs.ensureFile('/path/to/file.txt')
.then(() => console.log('File exists!'))
.catch(err => console.error(err));
Rimraf is a Node.js package that provides a simple way to delete files and directories with a UNIX command 'rm -rf' like functionality. It is less feature-rich compared to fs-extra, which provides a broader set of file system operations.
Mkdirp is a package that allows you to create a new directory and its parent directories if they do not exist (similar to the 'mkdir -p' command in UNIX). It is more focused than fs-extra, which includes this functionality as part of a larger suite of file system tools.
Graceful-fs is a drop-in replacement for the fs module that makes file system operations more robust by queuing them and retrying on certain types of errors. It does not add new methods like fs-extra but improves the reliability of existing ones.
Node-fs-extra is a fork of fs-extra that aims to provide the same functionality. However, fs-extra is more commonly used and actively maintained, making it the preferred choice for most developers.
fs-extra
adds file system methods that aren't included in the native fs
module and adds promise support to the fs
methods. It should be a drop in replacement for fs
.
I got tired of including mkdirp
, rimraf
, and ncp
in most of my projects.
npm install --save fs-extra
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')
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.
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)
}
NOTE: You can still use the native Node.js methods. They are promisified and copied over to fs-extra
.
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
.
If you like TypeScript, you can use fs-extra
with it: https://github.com/borisyankov/DefinitelyTyped/tree/master/fs-extra
If you want to watch for changes to files or directories, then you should use chokidar.
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
.
What's needed?
Note: If you make any big changes, you should definitely file an issue for discussion first.
fs-extra contains hundreds of tests.
npm run lint
: runs the linter (standard)npm run unit
: runs the unit testsnpm test
: runs both the linter and the testsIf 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.
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:
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)
.
fs-extra
wouldn't be possible without using the modules from the following authors:
Licensed under MIT
Copyright (c) 2011-2017 JP Richardson
FAQs
fs-extra contains methods that aren't included in the vanilla Node.js fs package. Such as recursive mkdir, copy, and remove.
The npm package fs-extra receives a total of 92,030,198 weekly downloads. As such, fs-extra popularity was classified as popular.
We found that fs-extra demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.