File system
- File system
- Promise example
- Callback example
- Synchronous example
- Promises API
- Class: FileHandle
- Event: 'close'
- filehandle.appendFile(data[, options])
- filehandle.chmod(mode)
- filehandle.chown(uid, gid)
- filehandle.close()
- filehandle.createReadStream([options])
- filehandle.createWriteStream([options])
- filehandle.datasync()
- filehandle.fd
- filehandle.pull([...transforms][, options])
- filehandle.pullSync([...transforms][, options])
- filehandle.read(buffer, offset, length, position)
- filehandle.read([options])
- filehandle.read(buffer[, options])
- filehandle.readableWebStream([options])
- filehandle.readFile(options)
- filehandle.readLines([options])
- filehandle.readv(buffers[, position])
- filehandle.stat([options])
- filehandle.sync()
- filehandle.truncate(len)
- filehandle.utimes(atime, mtime)
- filehandle.write(buffer, offset[, length[, position]])
- filehandle.write(buffer[, options])
- filehandle.write(string[, position[, encoding]])
- filehandle.writeFile(data, options)
- filehandle.writev(buffers[, position])
- filehandle.writer([options])
- filehandle[Symbol.asyncDispose]()
- fsPromises.access(path[, mode])
- fsPromises.appendFile(path, data[, options])
- fsPromises.chmod(path, mode)
- fsPromises.chown(path, uid, gid)
- fsPromises.copyFile(src, dest[, mode])
- fsPromises.cp(src, dest[, options])
- Class: FileHandle
<!--introduced_in=v0.10.0-->
Stability: 2 - Stable
<!--name=fs-->
<!-- source_link=lib/fs.js -->
The node:fs module enables interacting with the file system in a
way modeled on standard POSIX functions.
To use the promise-based APIs:
import * as fs from 'node:fs/promises';
const fs = require('node:fs/promises');
To use the callback and sync APIs:
import * as fs from 'node:fs';
const fs = require('node:fs');
All file system operations have synchronous, callback, and promise-based forms, and are accessible using both CommonJS syntax and ES6 Modules (ESM).
Promise example
Promise-based operations return a promise that is fulfilled when the asynchronous operation is complete.
import { unlink } from 'node:fs/promises';
try {
await unlink('/tmp/hello');
console.log('successfully deleted /tmp/hello');
} catch (error) {
console.error('there was an error:', error.message);
}
const { unlink } = require('node:fs/promises');
(async function(path) {
try {
await unlink(path);
console.log(`successfully deleted ${path}`);
} catch (error) {
console.error('there was an error:', error.message);
}
})('/tmp/hello');
Callback example
The callback form takes a completion callback function as its last
argument and invokes the operation asynchronously. The arguments passed to
the completion callback depend on the method, but the first argument is always
reserved for an exception. If the operation is completed successfully, then
the first argument is null or undefined.
import { unlink } from 'node:fs';
unlink('/tmp/hello', (err) => {
if (err) throw err;
console.log('successfully deleted /tmp/hello');
});
const { unlink } = require('node:fs');
unlink('/tmp/hello', (err) => {
if (err) throw err;
console.log('successfully deleted /tmp/hello');
});
The callback-based versions of the node:fs module APIs are preferable over
the use of the promise APIs when maximal performance (both in terms of
execution time and memory allocation) is required.
Synchronous example
The synchronous APIs block the Node.js event loop and further JavaScript
execution until the operation is complete. Exceptions are thrown immediately
and can be handled using try…catch, or can be allowed to bubble up.
import { unlinkSync } from 'node:fs';
try {
unlinkSync('/tmp/hello');
console.log('successfully deleted /tmp/hello');
} catch (err) {
// handle the error
}
const { unlinkSync } = require('node:fs');
try {
unlinkSync('/tmp/hello');
console.log('successfully deleted /tmp/hello');
} catch (err) {
// handle the error
}
Promises API
<!-- YAML
added: v10.0.0
changes:
- version: v14.0.0
pr-url: https://github.com/nodejs/node/pull/31553
description: Exposed as require('fs/promises').
- version:
- v11.14.0
- v10.17.0
pr-url: https://github.com/nodejs/node/pull/26581
description: This API is no longer experimental.
- version: v10.1.0
pr-url: https://github.com/nodejs/node/pull/20504
description: The API is accessible via require('fs').promises only.
-->
The fs/promises API provides asynchronous file system methods that return
promises.
The promise APIs use the underlying Node.js threadpool to perform file system operations off the event loop thread. These operations are not synchronized or threadsafe. Care must be taken when performing multiple concurrent modifications on the same file or data corruption may occur.
Class: FileHandle
<!-- YAML added: v10.0.0 -->
A {FileHandle} object is an object wrapper for a numeric file descriptor.
Instances of the {FileHandle} object are created by the fsPromises.open()
method.
All {FileHandle} objects are {EventEmitter}s.
If a {FileHandle} is not closed using the filehandle.close() method, it will
try to automatically close the file descriptor and emit a process warning,
helping to prevent memory leaks. Please do not rely on this behavior because
it can be unreliable and the file may not be closed. Instead, always explicitly
close {FileHandle}s. Node.js may change this behavior in the future.
Event: 'close'
<!-- YAML added: v15.4.0 -->
The 'close' event is emitted when the {FileHandle} has been closed and can no
longer be used.
filehandle.appendFile(data[, options])
<!-- YAML
added: v10.0.0
changes:
- version:
- v21.1.0
- v20.10.0
pr-url: https://github.com/nodejs/node/pull/50095
description: The flush option is now supported.
- version:
- v15.14.0
- v14.18.0
pr-url: https://github.com/nodejs/node/pull/37490
description: The data argument supports AsyncIterable, Iterable, and Stream.
- version: v14.0.0
pr-url: https://github.com/nodejs/node/pull/31030
description: The data parameter won't coerce unsupported input to
strings anymore.
-->
data{string|Buffer|TypedArray|DataView|AsyncIterable|Iterable}options{Object|string}encoding{string|null} Default:'utf8'signal{AbortSignal|undefined} allows aborting an in-progress writeFile. Default:undefined- Returns: {Promise} Fulfills with
undefinedupon success.
Alias of [filehandle.writeFile()][].
When operating on file handles, the mode cannot be changed from what it was set
to with [fsPromises.open()][]. Therefore, this is equivalent to
[filehandle.writeFile()][].
filehandle.chmod(mode)
<!-- YAML added: v10.0.0 -->
mode{integer} the file mode bit mask.- Returns: {Promise} Fulfills with
undefinedupon success.
Modifies the permissions on the file. See chmod(2).
filehandle.chown(uid, gid)
<!-- YAML added: v10.0.0 -->
uid{integer} The file's new owner's user id.gid{integer} The file's new group's group id.- Returns: {Promise} Fulfills with
undefinedupon success.
Changes the ownership of the file. A wrapper for chown(2).
filehandle.close()
<!-- YAML added: v10.0.0 -->
- Returns: {Promise} Fulfills with
undefinedupon success.
Closes the file handle after waiting for any pending operation on the handle to complete.
import { open } from 'node:fs/promises';
let filehandle;
try {
filehandle = await open('thefile.txt', 'r');
} finally {
await filehandle?.close();
}
filehandle.createReadStream([options])
<!-- YAML added: v16.11.0 -->
options{Object}encoding{string} Default:nullautoClose{boolean} Default:trueemitClose{boolean} Default:truestart{integer}end{integer} Default:InfinityhighWaterMark{integer} Default:64 * 1024signal{AbortSignal|undefined} Default:undefined- Returns: {fs.ReadStream}
options can include start and end values to read a range of bytes from
the file instead of the entire file. Both start and end are inclusive and
start counting at 0, allowed values are in the
[0, [Number.MAX_SAFE_INTEGER][]] range. If start is
omitted or undefined, filehandle.createReadStream() reads sequentially from
the current file position. The encoding can be any one of those accepted by
{Buffer}.
If the FileHandle points to a character device that only supports blocking
reads (such as keyboard or sound card), read operations do not finish until data
is available. This can prevent the process from exiting and the stream from
closing naturally.
By default, the stream will emit a 'close' event after it has been
destroyed. Set the emitClose option to false to change this behavior.
import { open } from 'node:fs/promises';
const fd = await open('/dev/input/event0');
// Create a stream from some character device.
const stream = fd.createReadStream();
setTimeout(() => {
stream.close(); // This may not close the stream.
// Artificially marking end-of-stream, as if the underlying resource had
// indicated end-of-file by itself, allows the stream to close.
// This does not cancel pending read operations, and if there is such an
// operation, the process may still not be able to exit successfully
// until it finishes.
stream.push(null);
stream.read(0);
}, 100);
If autoClose is false, then the file descriptor won't be closed, even if
there's an error. It is the application's responsibility to close it and make
sure there's no file descriptor leak. If autoClose is set to true (default
behavior), on 'error' or 'end' the file descriptor will be closed
automatically.
An example to read the last 10 bytes of a file which is 100 bytes long:
import { open } from 'node:fs/promises';
const fd = await open('sample.txt');
fd.createReadStream({ start: 90, end: 99 });
filehandle.createWriteStream([options])
<!-- YAML
added: v16.11.0
changes:
- version: v22.0.0
pr-url: https://github.com/nodejs/node/pull/52037
description: bump default highWaterMark.
- version:
- v21.0.0
- v20.10.0
pr-url: https://github.com/nodejs/node/pull/50093
description: The flush option is now supported.
-->
options{Object}encoding{string} Default:'utf8'autoClose{boolean} Default:trueemitClose{boolean} Default:truestart{integer}highWaterMark{number} Default: See [stream.getDefaultHighWaterMark()][].flush{boolean} Iftrue, the underlying file descriptor is flushed prior to closing it. Default:false.- Returns: {fs.WriteStream}
options may also include a start option to allow writing data at some
position past the beginning of the file, allowed values are in the
[0, [Number.MAX_SAFE_INTEGER][]] range. Modifying a file rather than
replacing it may require the flags open option to be set to r+ rather than
the default r. The encoding can be any one of those accepted by {Buffer}.
If autoClose is set to true (default behavior) on 'error' or 'finish'
the file descriptor will be closed automatically. If autoClose is false,
then the file descriptor won't be closed, even if there's an error.
It is the application's responsibility to close it and make sure there's no
file descriptor leak.
By default, the stream will emit a 'close' event after it has been
destroyed. Set the emitClose option to false to change this behavior.
filehandle.datasync()
<!-- YAML added: v10.0.0 -->
- Returns: {Promise} Fulfills with
undefinedupon success.
Forces all currently queued I/O operations associated with the file to the operating system's synchronized I/O completion state. Refer to the POSIX fdatasync(2) documentation for details.
Unlike filehandle.sync this method does not flush modified metadata.
filehandle.fd
<!-- YAML added: v10.0.0 -->
- Type: {number} The numeric file descriptor managed by the {FileHandle} object.
filehandle.pull([...transforms][, options])
<!-- YAML added: v25.9.0 -->
Stability: 1 - Experimental
...transforms{Function|Object} Optional transforms to apply via [stream/iter pull()][].options{Object}signal{AbortSignal}autoClose{boolean} Close the file handle when the stream ends. Default:false.start{number} Byte offset to begin reading from. When specified, reads use explicit positioning (preadsemantics). Default: current file position.limit{number} Maximum number of bytes to read before ending the iterator. Reads stop whenlimitbytes have been delivered or EOF is reached, whichever comes first. Default: read until EOF.chunkSize{number} Size in bytes of the buffer allocated for each read operation. Default:131072(128 KB).- Returns: {AsyncIterable} whose chunks fulfill with {Uint8Array[]}
Return the file contents as an async iterable using the
[node:stream/iter][] pull model. Reads are performed in chunkSize-byte
chunks (default 128 KB). If transforms are provided, they are applied
via [stream/iter pull()][].
The file handle is locked from the first read of the iterable, and unlocked when iteration completes, an error occurs, or the consumer breaks. An iterable that is never read does not lock the file handle.
This function is only available when the --experimental-stream-iter flag is
enabled.
import { open } from 'node:fs/promises';
import { text } from 'node:stream/iter';
import { compressGzip } from 'node:zlib/iter';
const fh = await open('input.txt', 'r');
// Read as text
console.log(await text(fh.pull({ autoClose: true })));
// Read 1 KB starting at byte 100
const fh2 = await open('input.txt', 'r');
console.log(await text(fh2.pull({ start: 100, limit: 1024, autoClose: true })));
// Read with compression
const fh3 = await open('input.txt', 'r');
const compressed = fh3.pull(compressGzip(), { autoClose: true });
const { open } = require('node:fs/promises');
const { text } = require('node:stream/iter');
const { compressGzip } = require('node:zlib/iter');
async function run() {
const fh = await open('input.txt', 'r');
// Read as text
console.log(await text(fh.pull({ autoClose: true })));
// Read 1 KB starting at byte 100
const fh2 = await open('input.txt', 'r');
console.log(await text(fh2.pull({ start: 100, limit: 1024, autoClose: true })));
// Read with compression
const fh3 = await open('input.txt', 'r');
const compressed = fh3.pull(compressGzip(), { autoClose: true });
}
run().catch(console.error);
filehandle.pullSync([...transforms][, options])
<!-- YAML added: v25.9.0 -->
Stability: 1 - Experimental
...transforms{Function|Object} Optional transforms to apply via [stream/iter pullSync()][].options{Object}autoClose{boolean} Close the file handle when the stream ends. Default:false.start{number} Byte offset to begin reading from. When specified, reads use explicit positioning. Default: current file position.limit{number} Maximum number of bytes to read before ending the iterator. Default: read until EOF.chunkSize{number} Size in bytes of the buffer allocated for each read operation. Default:131072(128 KB).- Returns: {Iterable} whose chunks return {Uint8Array[]}
Synchronous counterpart of [filehandle.pull()][]. Returns a sync iterable
that reads the file using synchronous I/O on the main thread. Reads are
performed in chunkSize-byte chunks (default 128 KB).
The file handle is locked from the first read of the iterable until iteration
ends, as with [filehandle.pull()][]. Unlike the async pull(), this method does not support AbortSignal since all
operations are synchronous.
This function is only available when the --experimental-stream-iter flag is
enabled.
import { open } from 'node:fs/promises';
import { textSync, pipeToSync } from 'node:stream/iter';
import { compressGzipSync, decompressGzipSync } from 'node:zlib/iter';
const fh = await open('input.txt', 'r');
// Read as text (sync)
console.log(textSync(fh.pullSync({ autoClose: true })));
// Sync compress pipeline: file -> gzip -> file
const src = await open('input.txt', 'r');
const dst = await open('output.gz', 'w');
pipeToSync(src.pullSync(compressGzipSync(), { autoClose: true }), dst.writer({ autoClose: true }));
const { open } = require('node:fs/promises');
const { textSync, pipeToSync } = require('node:stream/iter');
const { compressGzipSync, decompressGzipSync } = require('node:zlib/iter');
async function run() {
const fh = await open('input.txt', 'r');
// Read as text (sync)
console.log(textSync(fh.pullSync({ autoClose: true })));
// Sync compress pipeline: file -> gzip -> file
const src = await open('input.txt', 'r');
const dst = await open('output.gz', 'w');
pipeToSync(
src.pullSync(compressGzipSync(), { autoClose: true }),
dst.writer({ autoClose: true }),
);
}
run().catch(console.error);
filehandle.read(buffer, offset, length, position)
<!-- YAML
added: v10.0.0
changes:
- version: v21.0.0
pr-url: https://github.com/nodejs/node/pull/42835
description: Accepts bigint values as position.
-->
buffer{Buffer|TypedArray|DataView} A buffer that will be filled with the file data read.offset{integer} The location in the buffer at which to start filling. Default:0length{integer} The number of bytes to read. Default:buffer.byteLength - offsetposition{integer|bigint|null} The location where to begin reading data from the file. Ifnullor-1, data will be read from the current file position, and the position will be updated. Ifpositionis a non-negative integer, the current file position will remain unchanged. Default:null- Returns: {Promise} Fulfills upon success with an object with two properties:
bytesRead{integer} The number of bytes readbuffer{Buffer|TypedArray|DataView} A reference to the passed inbufferargument.
Reads data from the file and stores that in the given buffer.
If the file is not modified concurrently, the end-of-file is reached when the number of bytes read is zero.
filehandle.read([options])
<!-- YAML
added:
- v13.11.0
- v12.17.0
changes:
- version: v21.0.0
pr-url: https://github.com/nodejs/node/pull/42835
description: Accepts bigint values as position.
-->
options{Object}buffer{Buffer|TypedArray|DataView} A buffer that will be filled with the file data read. Default:Buffer.alloc(16384)offset{integer} The location in the buffer at which to start filling. Default:0length{integer} The number of bytes to read. Default:buffer.byteLength - offsetposition{integer|bigint|null} The location where to begin reading data from the file. Ifnullor-1, data will be read from the current file position, and the position will be updated. Ifpositionis a non-negative integer, the current file position will remain unchanged. Default::null- Returns: {Promise} Fulfills upon success with an object with two properties:
bytesRead{integer} The number of bytes readbuffer{Buffer|TypedArray|DataView} A reference to the passed inbufferargument.
Reads data from the file and stores that in the given buffer.
If the file is not modified concurrently, the end-of-file is reached when the number of bytes read is zero.
filehandle.read(buffer[, options])
<!-- YAML
added:
- v18.2.0
- v16.17.0
changes:
- version: v21.0.0
pr-url: https://github.com/nodejs/node/pull/42835
description: Accepts bigint values as position.
-->
buffer{Buffer|TypedArray|DataView} A buffer that will be filled with the file data read.options{Object}offset{integer} The location in the buffer at which to start filling. Default:0length{integer} The number of bytes to read. Default:buffer.byteLength - offsetposition{integer|bigint|null} The location where to begin reading data from the file. Ifnullor-1, data will be read from the current file position, and the position will be updated. Ifpositionis a non-negative integer, the current file position will remain unchanged. Default::null- Returns: {Promise} Fulfills upon success with an object with two properties:
bytesRead{integer} The number of bytes readbuffer{Buffer|TypedArray|DataView} A reference to the passed inbufferargument.
Reads data from the file and stores that in the given buffer.
If the file is not modified concurrently, the end-of-file is reached when the number of bytes read is zero.
filehandle.readableWebStream([options])
<!-- YAML added: v17.0.0 changes:
- version:
- v24.0.0
- v22.17.0 pr-url: https://github.com/nodejs/node/pull/57513 description: Marking the API stable.
- version:
- v23.8.0
- v22.15.0 pr-url: https://github.com/nodejs/node/pull/55461 description: Removed option to create a 'bytes' stream. Streams are now always 'bytes' streams.
-
version:
- v20.0.0
- v18.17.0 pr-url: https://github.com/nodejs/node/pull/46933 description: Added option to create a 'bytes' stream. -->
-
options{Object} autoClose{boolean} When true, causes the {FileHandle} to be closed when the stream is closed. Default:false- Returns: {ReadableStream}
Returns a byte-oriented ReadableStream that may be used to read the file's
contents.
An error will be thrown if this method is called more than once or is called
after the FileHandle is closed or closing.
import {
open,
} from 'node:fs/promises';
const file = await open('./some/file/to/read');
for await (const chunk of file.readableWebStream())
console.log(chunk);
await file.close();
const {
open,
} = require('node:fs/promises');
(async () => {
const file = await open('./some/file/to/read');
for await (const chunk of file.readableWebStream())
console.log(chunk);
await file.close();
})();
While the ReadableStream will read the file to completion, it will not
close the FileHandle automatically. User code must still call the
fileHandle.close() method unless the autoClose option is set to true.
filehandle.readFile(options)
<!-- YAML
added: v10.0.0
changes:
- version: v26.4.0
pr-url: https://github.com/nodejs/node/pull/63634
description: Added support for the buffer option.
-->
options{Object|string}encoding{string|null} Default:nullsignal{AbortSignal} allows aborting an in-progress readFilebuffer{Buffer|TypedArray|DataView|Function} A buffer to read into, or a function called with the file size that returns the buffer.- Returns: {Promise} Fulfills upon a successful read with the contents of the
file. If no encoding is specified (using
options.encoding), the data is returned as a {Buffer} object. Otherwise, the data will be a string.
Asynchronously reads the entire contents of a file.
If options is a string, then it specifies the encoding.
If buffer is provided and no encoding is specified, the returned {Buffer} is
a view over the supplied buffer containing only the bytes read. If the
supplied buffer is too small to contain the entire file, the operation will
fail.
The {FileHandle} has to support reading.
If one or more filehandle.read() calls are made on a file handle and then a
filehandle.readFile() call is made, the data will be read from the current
position till the end of the file. It doesn't always read from the beginning
of the file.
An example using the buffer option with a pre-allocated buffer:
import { Buffer } from 'node:buffer';
import { open } from 'node:fs/promises';
const file = await open('./some/file/to/read');
try {
const buf = Buffer.alloc(16384);
const contents = await file.readFile({ buffer: buf });
console.log(contents); // A view over `buf` containing only the bytes read
} finally {
await file.close();
}
An example using the buffer option with a function returning a buffer:
import { Buffer } from 'node:buffer';
import { open } from 'node:fs/promises';
const file = await open('./some/file/to/read');
try {
const contents = await file.readFile({
buffer: (size) => Buffer.alloc(size),
});
console.log(contents);
} finally {
await file.close();
}
filehandle.readLines([options])
<!-- YAML added: v18.11.0 -->
options{Object}encoding{string} Default:nullautoClose{boolean} Default:trueemitClose{boolean} Default:truestart{integer}end{integer} Default:InfinityhighWaterMark{integer} Default:64 * 1024- Returns: {readline.InterfaceConstructor}
Convenience method to create a readline interface and stream over the file.
See [filehandle.createReadStream()][] for the options.
import { open } from 'node:fs/promises';
const file = await open('./some/file/to/read');
for await (const line of file.readLines()) {
console.log(line);
}
const { open } = require('node:fs/promises');
(async () => {
const file = await open('./some/file/to/read');
for await (const line of file.readLines()) {
console.log(line);
}
})();
filehandle.readv(buffers[, position])
<!-- YAML added: - v13.13.0 - v12.17.0 -->
buffers{Buffer[]|TypedArray[]|DataView[]}position{integer|null} The offset from the beginning of the file where the data should be read from. Ifpositionis not anumber, the data will be read from the current position. Default:null- Returns: {Promise} Fulfills upon success an object containing two properties:
bytesRead{integer} the number of bytes readbuffers{Buffer[]|TypedArray[]|DataView[]} property containing a reference to thebuffersinput.
Read from a file and write to an array of {ArrayBufferView}s
filehandle.stat([options])
<!-- YAML
added: v10.0.0
changes:
- version: v26.1.0
pr-url: https://github.com/nodejs/node/pull/57775
description: Now accepts an additional signal property to allow aborting the operation.
- version: v10.5.0
pr-url: https://github.com/nodejs/node/pull/20220
description: Accepts an additional options object to specify whether the numeric values returned should be bigint.
-->
options{Object}bigint{boolean} Whether the numeric values in the returned {fs.Stats} object should bebigint. Default:false.signal{AbortSignal} An AbortSignal to cancel the operation. Default:undefined.- Returns: {Promise} Fulfills with an {fs.Stats} for the file.
filehandle.sync()
<!-- YAML added: v10.0.0 -->
- Returns: {Promise} Fulfills with
undefinedupon success.
Request that all data for the open file descriptor is flushed to the storage device. The specific implementation is operating system and device specific. Refer to the POSIX fsync(2) documentation for more detail.
filehandle.truncate(len)
<!-- YAML added: v10.0.0 -->
len{integer} Default:0- Returns: {Promise} Fulfills with
undefinedupon success.
Truncates the file.
If the file was larger than len bytes, only the first len bytes will be
retained in the file.
The following example retains only the first four bytes of the file:
import { open } from 'node:fs/promises';
let filehandle = null;
try {
filehandle = await open('temp.txt', 'r+');
await filehandle.truncate(4);
} finally {
await filehandle?.close();
}
If the file previously was shorter than len bytes, it is extended, and the
extended part is filled with null bytes ('\0'):
If len is negative then 0 will be used.
filehandle.utimes(atime, mtime)
<!-- YAML added: v10.0.0 -->
atime{number|string|Date}mtime{number|string|Date}- Returns: {Promise}
Change the file system timestamps of the object referenced by the {FileHandle} then fulfills the promise with no arguments upon success.
filehandle.write(buffer, offset[, length[, position]])
<!-- YAML
added: v10.0.0
changes:
- version: v14.0.0
pr-url: https://github.com/nodejs/node/pull/31030
description: The buffer parameter won't coerce unsupported input to
buffers anymore.
-->
buffer{Buffer|TypedArray|DataView}offset{integer} The start position from withinbufferwhere the data to write begins.length{integer} The number of bytes frombufferto write. Default:buffer.byteLength - offsetposition{integer|null} The offset from the beginning of the file where the data frombuffershould be written. Ifpositionis not anumber, the data will be written at the current position. See the POSIX pwrite(2) documentation for more detail. Default:null- Returns: {Promise}
Write buffer to the file.
The promise is fulfilled with an object containing two properties:
bytesWritten{integer} the number of bytes writtenbuffer{Buffer|TypedArray|DataView} a reference to thebufferwritten.
It is unsafe to use filehandle.write() multiple times on the same file
without waiting for the promise to be fulfilled (or rejected). For this
scenario, use [filehandle.createWriteStream()][].
On Linux, positional writes do not work when the file is opened in append mode. The kernel ignores the position argument and always appends the data to the end of the file.
filehandle.write(buffer[, options])
<!-- YAML added: - v18.3.0 - v16.17.0 -->
buffer{Buffer|TypedArray|DataView}options{Object}offset{integer} Default:0length{integer} Default:buffer.byteLength - offsetposition{integer|null} Default:null- Returns: {Promise}
Write buffer to the file.
Similar to the above filehandle.write function, this version takes an
optional options object. If no options object is specified, it will
default with the above values.
filehandle.write(string[, position[, encoding]])
<!-- YAML
added: v10.0.0
changes:
- version: v14.0.0
pr-url: https://github.com/nodejs/node/pull/31030
description: The string parameter won't coerce unsupported input to
strings anymore.
-->
string{string}position{integer|null} The offset from the beginning of the file where the data fromstringshould be written. Ifpositionis not anumberthe data will be written at the current position. See the POSIX pwrite(2) documentation for more detail. Default:nullencoding{string} The expected string encoding. Default:'utf8'- Returns: {Promise}
Write string to the file. If string is not a string, the promise is
rejected with an error.
The promise is fulfilled with an object containing two properties:
bytesWritten{integer} the number of bytes writtenbuffer{string} a reference to thestringwritten.
It is unsafe to use filehandle.write() multiple times on the same file
without waiting for the promise to be fulfilled (or rejected). For this
scenario, use [filehandle.createWriteStream()][].
On Linux, positional writes do not work when the file is opened in append mode. The kernel ignores the position argument and always appends the data to the end of the file.
filehandle.writeFile(data, options)
<!-- YAML
added: v10.0.0
changes:
- version:
- v15.14.0
- v14.18.0
pr-url: https://github.com/nodejs/node/pull/37490
description: The data argument supports AsyncIterable, Iterable, and Stream.
- version: v14.0.0
pr-url: https://github.com/nodejs/node/pull/31030
description: The data parameter won't coerce unsupported input to
strings anymore.
-->
data{string|Buffer|TypedArray|DataView|AsyncIterable|Iterable}options{Object|string}encoding{string|null} The expected character encoding whendatais a string. Default:'utf8'signal{AbortSignal|undefined} allows aborting an in-progress writeFile. Default:undefined- Returns: {Promise}
Asynchronously writes data to a file, replacing the file if it already exists.
data can be a string, a buffer, an {AsyncIterable}, or an {Iterable} object.
The promise is fulfilled with no arguments upon success.
If options is a string, then it specifies the encoding.
The {FileHandle} has to support writing.
It is unsafe to use filehandle.writeFile() multiple times on the same file
without waiting for the promise to be fulfilled (or rejected).
If one or more filehandle.write() calls are made on a file handle and then a
filehandle.writeFile() call is made, the data will be written from the
current position till the end of the file. It doesn't always write from the
beginning of the file.
filehandle.writev(buffers[, position])
<!-- YAML added: v12.9.0 -->
buffers{Buffer[]|TypedArray[]|DataView[]}position{integer|null} The offset from the beginning of the file where the data frombuffersshould be written. Ifpositionis not anumber, the data will be written at the current position. Default:null- Returns: {Promise}
Write an array of {ArrayBufferView}s to the file.
The promise is fulfilled with an object containing a two properties:
bytesWritten{integer} the number of bytes writtenbuffers{Buffer[]|TypedArray[]|DataView[]} a reference to thebuffersinput.
It is unsafe to call writev() multiple times on the same file without waiting
for the promise to be fulfilled (or rejected).
On Linux, positional writes don't work when the file is opened in append mode. The kernel ignores the position argument and always appends the data to the end of the file.
filehandle.writer([options])
<!-- YAML added: v25.9.0 -->
Stability: 1 - Experimental
options{Object}autoClose{boolean} Close the file handle when the writer ends or fails. Default:false.start{number} Byte offset to start writing at. When specified, writes use explicit positioning. Default: current file position.limit{number} Maximum number of bytes the writer will accept. Async writes (write(),writev()) that would exceed the limit reject withERR_OUT_OF_RANGE. Sync writes (writeSync(),writevSync()) returnfalse. Default: no limit.chunkSize{number} Maximum chunk size in bytes for synchronous write operations. Writes larger than this threshold fall back to async I/O. Set this to match the reader'schunkSizefor optimalpipeTo()performance. Default:131072(128 KB).- Returns: {Object}
write(chunk[, options]){Function} Returns {Promise}. AcceptsUint8Array,Buffer, or string (UTF-8 encoded).chunk{Buffer|TypedArray|DataView|string}options{Object}signal{AbortSignal} If the signal is already aborted, the write rejects withAbortErrorwithout performing I/O.
writev(chunks[, options]){Function} Returns {Promise}. Uses scatter/gather I/O via a singlewritev()syscall. Accepts mixedUint8Array/string arrays.chunks{Buffer[]|TypedArray[]|DataView[]|string[]}options{Object}signal{AbortSignal} If the signal is already aborted, the write rejects withAbortErrorwithout performing I/O.
writeSync(chunk){Function} Returns {boolean}. Attempts a synchronous write. Returnstrueif the write succeeded,falseif the caller should fall back to asyncwrite(). Returnsfalsewhen: the writer is closed/errored, an async operation is in flight, the chunk exceedschunkSize, or the write would exceedlimit.chunk{Buffer|TypedArray|DataView|string}
writevSync(chunks){Function} Returns {boolean}. Synchronous batch write. Same fallback semantics aswriteSync().chunks{Buffer[]|TypedArray[]|DataView[]|string[]}
end([options]){Function} Returns {Promise}, fulfills with the total number of bytes written. Idempotent: returnstotalBytesWrittenif already closed, returns the pending promise if already closing. Rejects if the writer is in an errored state.options{Object}signal{AbortSignal} If the signal is already aborted,end()rejects withAbortErrorand the writer remains open.
endSync(){Function} Returns {number|number} total bytes written on success,-1if the writer is errored or an async operation is in flight. Idempotent when already closed.fail(reason){Function} Puts the writer into a terminal error state. Synchronous. If the writer is already closed or errored, this is a no-op. IfautoCloseis true, closes the file handle synchronously.
Return a [node:stream/iter][] writer backed by this file handle.
The writer supports both Symbol.asyncDispose and Symbol.dispose:
await using w = fh.writer()— if the writer is still open (noend()called),asyncDisposecallsfail(). Ifend()is pending, it waits for it to complete.using w = fh.writer()— callsfail()unconditionally.
Async writes (write() and writev()) that are started without awaiting the
previous one are performed one at a time, in the order they were called, so
they never overlap in the file. A queued write is not performed if the writer
fails, or its signal aborts, before its turn.
The writeSync() and writevSync() methods enable the try-sync fast path
used by [stream/iter pipeTo()][]. When the reader's chunk size matches the
writer's chunkSize, all writes in a pipeTo() pipeline complete
synchronously with zero promise overhead.
This function is only available when the --experimental-stream-iter flag is
enabled.
import { open } from 'node:fs/promises';
import { from, pipeTo } from 'node:stream/iter';
import { compressGzip } from 'node:zlib/iter';
// Async pipeline
const fh = await open('output.gz', 'w');
await pipeTo(from('Hello!'), compressGzip(), fh.writer({ autoClose: true }));
// Sync pipeline with limit
const src = await open('input.txt', 'r');
const dst = await open('output.txt', 'w');
const w = dst.writer({ limit: 1024 * 1024 }); // Max 1 MB
await pipeTo(src.pull({ autoClose: true }), w);
await w.end();
await dst.close();
const { open } = require('node:fs/promises');
const { from, pipeTo } = require('node:stream/iter');
const { compressGzip } = require('node:zlib/iter');
async function run() {
// Async pipeline
const fh = await open('output.gz', 'w');
await pipeTo(from('Hello!'), compressGzip(), fh.writer({ autoClose: true }));
// Sync pipeline with limit
const src = await open('input.txt', 'r');
const dst = await open('output.txt', 'w');
const w = dst.writer({ limit: 1024 * 1024 }); // Max 1 MB
await pipeTo(src.pull({ autoClose: true }), w);
await w.end();
await dst.close();
}
run().catch(console.error);
filehandle[Symbol.asyncDispose]()
<!-- YAML added: - v20.4.0 - v18.18.0 changes: - version: v24.2.0 pr-url: https://github.com/nodejs/node/pull/58467 description: No longer experimental. -->
- Returns: {Promise}
Calls filehandle.close() and returns a promise that fulfills when the
filehandle is closed.
This method enables the filehandle to be used with [await using][], which
will automatically close the file when the scope exits. For more information,
see the [MDN documentation on using statements][using].
fsPromises.access(path[, mode])
<!-- YAML added: v10.0.0 -->
path{string|Buffer|URL}mode{integer} Default:fs.constants.F_OK- Returns: {Promise} Fulfills with
undefinedupon success.
Tests a user's permissions for the file or directory specified by path.
The mode argument is an optional integer that specifies the accessibility
checks to be performed. mode should be either the value fs.constants.F_OK
or a mask consisting of the bitwise OR of any of fs.constants.R_OK,
fs.constants.W_OK, and fs.constants.X_OK (e.g.
fs.constants.W_OK | fs.constants.R_OK). Check [File access constants][] for
possible values of mode.
If the accessibility check is successful, the promise is fulfilled with no
value. If any of the accessibility checks fail, the promise is rejected
with an {Error} object. The following example checks if the file
/etc/passwd can be read and written by the current process.
import { access, constants } from 'node:fs/promises';
try {
await access('/etc/passwd', constants.R_OK | constants.W_OK);
console.log('can access');
} catch {
console.error('cannot access');
}
Using fsPromises.access() to check for the accessibility of a file before
calling fsPromises.open() is not recommended. Doing so introduces a race
condition, since other processes may change the file's state between the two
calls. Instead, user code should open/read/write the file directly and handle
the error raised if the file is not accessible.
fsPromises.appendFile(path, data[, options])
<!-- YAML
added: v10.0.0
changes:
- version:
- v21.1.0
- v20.10.0
pr-url: https://github.com/nodejs/node/pull/50095
description: The flush option is now supported.
- version:
- v15.14.0
- v14.18.0
pr-url: https://github.com/nodejs/node/pull/37490
description: The data argument supports AsyncIterable, Iterable, and Stream.
-->
path{string|Buffer|URL|FileHandle} filename or {FileHandle}data{string|Buffer|TypedArray|DataView|AsyncIterable|Iterable}options{Object|string}encoding{string|null} Default:'utf8'mode{integer} Default:0o666flag{string} See [support of file systemflags][]. Default:'a'.flush{boolean} Iftrue, the underlying file descriptor is flushed prior to closing it. Default:false.- Returns: {Promise} Fulfills with
undefinedupon success.
Asynchronously append data to a file, creating the file if it does not yet
data can be a string, a buffer, an {AsyncIterable}, or an {Iterable} object.
If options is a string, then it specifies the encoding.
The mode option only affects the newly created file. See [fs.open()][]
for more details.
The path may be specified as a {FileHandle} that has been opened
for appending (using fsPromises.open()).
fsPromises.chmod(path, mode)
<!-- YAML added: v10.0.0 -->
path{string|Buffer|URL}mode{string|integer}- Returns: {Promise} Fulfills with
undefinedupon success.
Changes the permissions of a file.
fsPromises.chown(path, uid, gid)
<!-- YAML added: v10.0.0 -->
path{string|Buffer|URL}uid{integer}gid{integer}- Returns: {Promise} Fulfills with
undefinedupon success.
Changes the ownership of a file.
fsPromises.copyFile(src, dest[, mode])
<!-- YAML
added: v10.0.0
changes:
- version: v14.0.0
pr-url: https://github.com/nodejs/node/pull/27044
description: Changed flags argument to mode and imposed
stricter type validation.
-->
src{string|Buffer|URL} source filename to copydest{string|Buffer|URL} destination filename of the copy operationmode{integer} Optional modifiers that specify the behavior of the copy operation. It is possible to create a mask consisting of the bitwise OR of two or more values (e.g.fs.constants.COPYFILE_EXCL | fs.constants.COPYFILE_FICLONE) Default:0.fs.constants.COPYFILE_EXCL: The copy operation will fail ifdestalready exists.fs.constants.COPYFILE_FICLONE: The copy operation will attempt to create a copy-on-write reflink. If the platform does not support copy-on-write, then a fallback copy mechanism is used.fs.constants.COPYFILE_FICLONE_FORCE: The copy operation will attempt to create a copy-on-write reflink. If the platform does not support copy-on-write, then the operation will fail.- Returns: {Promise} Fulfills with
undefinedupon success.
Asynchronously copies src to dest. By default, dest is overwritten if it
already exists.
Symbolic links are followed. If src is a symbolic link, the target file is
copied. If dest is a symbolic link, the target file is overwritten unless
mode contains fs.constants.COPYFILE_EXCL.
No guarantees are made about the atomicity of the copy operation. If an error occurs after the destination file has been opened for writing, an attempt will be made to remove the destination.
import { copyFile, constants } from 'node:fs/promises';
try {
await copyFile('source.txt', 'destination.txt');
console.log('source.txt was copied to destination.txt');
} catch {
console.error('The file could not be copied');
}
// By using COPYFILE_EXCL, the operation will fail if destination.txt exists.
try {
await copyFile('source.txt', 'destination.txt', constants.COPYFILE_EXCL);
console.log('source.txt was copied to destination.txt');
} catch {
console.error('The file could not be copied');
}
fsPromises.cp(src, dest[, options])
<!-- YAML
added: v16.7.0
changes:
- version: v22.3.0
pr-url: https://github.com/nodejs/node/pull/53127
description: This API is no longer experimental.
- version:
- v20.1.0
- v18.17.0
pr-url: https://github.com/nodejs/node/pull/47084
description: Accept an additional mode option to specify
the copy behavior as the mode argument of fs.copyFile().
- version:
- v17.6.0
- v16.15.0
pr-url: https://github.com/nodejs/node/pull/41819
description: Accepts an additional verbatimSymlinks option to specify
whether to perform path resolution for symlinks.
-->
src{string|URL} so
(本文超出站点单文档体积上限,已截断)
