fs-extra contains methods that aren't included in the vanilla Node.js fs package. Such as mkdir -p, cp -r, and rm -rf. 

fs-extra contains methods that aren't included in the vanilla Node.js fs package. Such as recursive mkdir, copy, and remove.

jprichardson

ryanzim

manidlou

fs-extra

fs-extra contains methods that aren't included in the vanilla Node.js fs package. Such as mkdir -p, cp -r, and rm -rf.

Error

Ignore

Warn

License

Maintenance

Miscellaneous

Quality

Supply chain risk

Vulnerability

Admins only

Organization members

Dashboard

<upgradeLink>Upgrade</upgradeLink> to access this feature

About

Blog

Socket CLI

Customers

Socket Dependency Search

Docs

Socket for GitHub

Love

Impersonation Mode Active

Update your browser to the latest version for the best experience.

Your web browser is outdated

Use another browser for the best experience.

Your web browser is unsupported

{{count, number}} commits last two months

{{count, number}} critical severity alert

{{count, number}} critical severity alerts

{{count, number}} dependency vulnerability

{{count, number}} dependency vulnerabilities

{{count, number}} development dependencies

{{count, number}} transitive dependencies

{{count, number}} version published last month

{{count, number}} versions published last month

{{count, number}} version published in last two months

{{count, number}} versions published in last two months

{{count, number}} version published last week

{{count, number}} versions published last week

{{count, number}} version published last year

{{count, number}} versions published last year

Socket undergoes annual SOC2 Type II audits. Socket customers can request a copy of the full SOC2 Type II report.

Allows organization owners and admins to access detailed records of actions taken by members of their organization, complete with timestamps.

Prevent compromised packages from infiltrating your supply chain by monitoring for changes in real-time.

Join our Discord community to get help from Socket engineers and other Socket users.

Compare millions of open source packages on socket.dev

Detect malicious code and risky behavior (e.g. network) in your dependencies using "deep package inspection"

All data is encrypted in transit and at rest using industry standard encryption algorithms.

Get a dedicated Socket account manager and access to Socket’s Customer Success team.

Get dedicated support from Socket engineers via email and Slack.

"Shift left" with the Socket Chrome extension and give intervene early, before developers choose risky or low quality dependencies.

Catch developers using risky dependencies and give them a "speed bump" to encourage good behavior

Install the Socket GitHub app to receive real-time dependency scanning and reports with every pull request.

Integrate Socket into your GitHub SCM to prevent risky dependencies from being installed.

Socket scans for vulnerabilities in your dependencies, including CVEs, security advisories, and more.

Socket supports dependencies in many languages, with most popular ecosystems coming in 2024. We've got you covered no matter what languages you use.

Enforce license policies across your organization

Receive a Microsoft Teams message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Get help migrating from Socket's free plan to Socket's paid plans.

Run Socket on-premises or in your own cloud environment.

Query for any dependency (at any version) across your entire organization

Integrate Socket into your CI/CD pipeline to prevent risky dependencies from being deployed to production.

Analyze an entire project to find supply chain risks

Tag projects to organize and filter your projects

Restrict access based on the roles of individual users within an organization.

Receive a Slack message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket is SOC2 Type II compliant and undergoes annual audits.

The Socket CLI allows teams to prevent risky dependencies from being installed, and to get dependency insights from the command line.

Socket supports SAML SSO for single sign-on and identity management.

Integrate Socket into your VS Code IDE to prevent risky dependencies from being installed.

Get a POST request anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket will analyzed your SBOMs up to a maximum number of dependencies.

API that allows you to analyze a project, lookup package scores and alerts, and more.

Create API tokens to authenticate with the Socket API and CLI.

The number of developers in your team. A developer is someone who made a commit to your organization's repositories scanned by Socket in the past month.

Use Socket to protect your private repositories.

Socket is always free for open source projects.

Socket retains all reporting data for 3 months, 1 year, or a custom term of your choice.

Access the threat feed that powers Socket.

Unlimited scale, self-hosting, and priority support for large teams.

For open-source projects, individuals, and small teams.

For growing teams with enhanced scale, security, and support.

There is a package with a similar name that is downloaded much more often.

There are packages with similar names that are downloaded much more often.

This may not be the package you want!

Instance

Alert Locations

Package

The {{ecosystem}} package {{- packageName}} receives a total of <strong>{{numWeeklyDownloadCount, number}}</strong> weekly downloads. As such, {{- packageName}} popularity was classified as <strong>{{popularity}}</strong>.

Is {{- packageName}} popular?

Is {{- packageName}} safe to use?

Is {{- packageName}} well maintained?

What is {{- packageName}}?

{{packageDescription}}Version: {{versionString}} was published by {{publisherName}}. Start using Socket to analyze {{- packageName}} and its {{dependencyCount, number}} dependencies to secure your app from supply chain attacks.

Sorry, it seems this package was removed from the registry

Package was removed

This package version has been unpublished, mostly likely due to security reasons

Package version was removed

Provide a detailed description of the malware...

Socket fights vulnerabilities and provides visibility, defense-in-depth, and proactive supply chain protection for JavaScript, Python, and Go dependencies.

Socket - Secure your dependencies. Ship with confidence.

Compare versions

{{- packageName}} - npm Package Compare versions

- Reverted [`5597bd`](https://github.com/jprichardson/node-fs-extra/commit/5597bd5b67f7d060f5f5bf26e9635be48330f5d7), this broke compatibility with Node.js versions v4+ but less than `v4.5.0`.

- Remove `Buffer.alloc()` usage in `moveSync()`.

Thanks to [Mani Maghsoudlou (@manidlou)](https://github.com/manidlou) & [Jan Peer Stöcklmair (@JPeer264)](https://github.com/JPeer264) for their extraordinary help with this release!

- `moveSync()` See [#309], [#381](https://github.com/jprichardson/node-fs-extra/pull/381). ([@manidlou](https://github.com/manidlou))

- `copy()` and `copySync()`'s `filter` option now gets the destination path passed as the second parameter. [#366](https://github.com/jprichardson/node-fs-extra/pull/366) ([@manidlou](https://github.com/manidlou))

- Use `Buffer.alloc()` instead of deprecated `new Buffer()` in `copySync()`. [#380](https://github.com/jprichardson/node-fs-extra/pull/380) ([@manidlou](https://github.com/manidlou))

- Refactored entire codebase to use ES6 features supported by Node.js v4+ [#355](https://github.com/jprichardson/node-fs-extra/issues/355). [(@JPeer264)](https://github.com/JPeer264)

- Refactored docs. ([@manidlou](https://github.com/manidlou))

- `move()` shouldn't error out when source and dest are the same. [#377](https://github.com/jprichardson/node-fs-extra/issues/377), [#378](https://github.com/jprichardson/node-fs-extra/pull/378) ([@jdalton](https://github.com/jdalton))

- **BREAKING:** Removed support for Node `v0.12`. The Node foundation stopped officially supporting it

- **BREAKING:** Remove `walk()` and `walkSync()`. `walkSync()` was only part of `fs-extra` for a little

over two months. Use [klaw](https://github.com/jprichardson/node-klaw) instead of `walk()`, in fact, `walk()` was just

an alias to klaw. For `walkSync()` use [klaw-sync](https://github.com/mawni/node-klaw-sync). See: [#338], [#339]

- **BREAKING:** Renamed `clobber` to `overwrite`. This affects `copy()`, `copySync()`, and `move()`. [#330], [#333]

- Apply filters to directories in `copySync()` like in `copy()`. [#324]

- A specific condition when disk is under heavy use, `copy()` can fail. [#326]

After five years of development, we finally have reach the 1.0.0 milestone! Big thanks goes

to [Ryan Zim](https://github.com/RyanZim) for leading the charge on this release!

- **BREAKING**: dropped Node v0.10 support.

- disabled `rimaf` globbing, wasn't used. [#280]

- deprecate `copy()/copySync()` option `filter` if it's a `RegExp`. `filter` should now be a function.

- inline `rimraf`. This is temporary and was done because `rimraf` depended upon the beefy `glob` which `fs-extra` does not use. [#300]

- bug fix proper closing of file handle on `utimesMillis()` [#271]

- proper escaping of files with dollar signs [#291]

- `copySync()` failed if user didn't own file. [#199], [#301]

- Brought back Node v0.10 support. I didn't realize there was still demand. Official support will end **2016-10-01**.

- **BREAKING**: removed support for Node v0.10. If you still want to use Node v0.10, everything should work except for `ensureLink()/ensureSymlink()`. Node v0.12 is still supported but will be dropped in the near future as well.

- **BREAKING**: removed `createOutputStream()`. Use https://www.npmjs.com/package/create-output-stream. See: [#192][#192]

- `mkdirs()/mkdirsSync()` check for invalid win32 path chars. See: [#209][#209], [#237][#237]

- `mkdirs()/mkdirsSync()` if drive not mounted, error. See: [#93][#93]

- add `dereference` option to `copySync()`. [#235][#235]

- fixed `copy()` if source and dest are the same. [#230][#230]

- fixed if `emptyDir()` does not have a callback: [#229][#229]

- `copy()` with two arguments (w/o callback) was broken. See: [#215][#215]

- `copySync()` made `preserveTimestamps` default consistent with `copy()` which is `false`. See: [#208][#208]

- fixed `copy()` hangup in copying blockDevice / characterDevice / `/dev/null`. See: [#193][#193]

- fixed `outputJson{Sync}()` spacing adherence to `fs.spaces`

function copyFileSync (srcFile, destFile, options) {

  const errorOnExist = options.errorOnExist

  const preserveTimestamps = options.preserveTimestamps

      throw new Error(`${destFile} already exists`)

  const fdw = fs.openSync(destFile, 'w', stat.mode)

    bytesRead = fs.readSync(fdr, _buff, 0, BUF_LENGTH, pos)

    fs.writeSync(fdw, _buff, 0, bytesRead)

    fs.futimesSync(fdw, stat.atime, stat.mtime)

const copySync = require('../copy-sync').copySync

const removeSync = require('../remove').removeSync

const mkdirpSync = require('../mkdirs').mkdirsSync

  const overwrite = options.overwrite || options.clobber || false

  if (isSrcSubdir(src, dest)) throw new Error(`Cannot move '${src}' into itself '${dest}'.`)

        if (err.code === 'ENOTEMPTY' || err.code === 'EEXIST' || err.code === 'EPERM') {

          options.overwrite = false // just overwriteed it, no need to do it again

          return moveSync(src, dest, options)

        if (err.code !== 'EXDEV') throw err

        return moveSyncAcrossDevice(src, dest, overwrite)

        if (err.code === 'EXDEV' || err.code === 'EISDIR' || err.code === 'EPERM' || err.code === 'ENOTSUP') {

          return moveSyncAcrossDevice(src, dest, overwrite)

function moveSyncAcrossDevice (src, dest, overwrite) {

    return moveDirSyncAcrossDevice(src, dest, overwrite)

    return moveFileSyncAcrossDevice(src, dest, overwrite)

function moveFileSyncAcrossDevice (src, dest, overwrite) {

  const fdw = fs.openSync(dest, flags, stat.mode)

function moveDirSyncAcrossDevice (src, dest, overwrite) {

// return true if dest is a subdir of src, otherwise false.

// extract dest base dir and check if that is the same as src basename

    return fs.statSync(src).isDirectory() &&

           dest.split(path.dirname(src) + path.sep)[1].split(path.sep)[0] === path.basename(src)

  "description": "fs-extra contains methods that aren't included in the vanilla Node.js fs package. Such as mkdir -p, cp -r, and rm -rf.",

  "homepage": "https://github.com/jprichardson/node-fs-extra",

    "url": "https://github.com/jprichardson/node-fs-extra"

  "author": "JP Richardson <jprichardson@gmail.com>",

    "coverage": "istanbul cover -i 'lib/**' -x '**/__tests__/**' test.js",

    "coveralls": "npm run coverage && coveralls < coverage/lcov.info",

    "test-find": "find ./lib/**/__tests__ -name *.test.js | xargs mocha",

    "test": "npm run lint && npm run unit",

		@@ -0,1 +1,9 @@
		2.1.1 / 2017-03-15
		------------------

		### Fixed

		- Reverted [`5597bd`](https://github.com/jprichardson/node-fs-extra/commit/5597bd5b67f7d060f5f5bf26e9635be48330f5d7), this broke compatibility with Node.js versions v4+ but less than `v4.5.0`.
		- Remove `Buffer.alloc()` usage in `moveSync()`.

		2.1.0 / 2017-03-15
		@@ -2,0 +10,0 @@ ------------------

		@@ -6,3 +6,3 @@ 'use strict'
		const BUF_LENGTH = 64 * 1024
		const _buff = Buffer.alloc(BUF_LENGTH)
		const _buff = new Buffer(BUF_LENGTH)

		@@ -9,0 +9,0 @@ function copyFileSync (srcFile, destFile, options) {

		@@ -63,3 +63,3 @@ 'use strict'
		const BUF_LENGTH = 64 * 1024
		const _buff = Buffer.alloc(BUF_LENGTH)
		const _buff = new Buffer(BUF_LENGTH)

		@@ -66,0 +66,0 @@ const flags = overwrite ? 'w' : 'wx'

		{
		"name": "fs-extra",
		"version": "2.1.0",
		"version": "2.1.1",
		"description": "fs-extra contains methods that aren't included in the vanilla Node.js fs package. Such as mkdir -p, cp -r, and rm -rf.",
		@@ -60,6 +60,3 @@ "homepage": "https://github.com/jprichardson/node-fs-extra",
		"unit": "node test.js"
		},
		"engines": {
		"node": ">=4.5.0"
		}
		}

Fixed alerts

Improved metrics