Asynchronously writes buffer
to the file referenced by the supplied file descriptor.
A file descriptor.
The part of the buffer to be written. If not supplied, defaults to 0
.
The number of bytes to write. If not supplied, defaults to buffer.length - offset
.
Asynchronously writes buffer
to the file referenced by the supplied file descriptor.
A file descriptor.
The part of the buffer to be written. If not supplied, defaults to 0
.
Asynchronously writes buffer
to the file referenced by the supplied file descriptor.
A file descriptor.
Asynchronously writes string
to the file referenced by the supplied file descriptor.
A file descriptor.
A string to write.
The offset from the beginning of the file where this data should be written. If not supplied, defaults to the current position.
The expected string encoding.
Asynchronously writes string
to the file referenced by the supplied file descriptor.
A file descriptor.
A string to write.
The offset from the beginning of the file where this data should be written. If not supplied, defaults to the current position.
Asynchronously writes string
to the file referenced by the supplied file descriptor.
A file descriptor.
A string to write.
Write buffer
to the file specified by fd
. If buffer
is a normal object, it
must have an own toString
function property.
offset
determines the part of the buffer to be written, and length
is
an integer specifying the number of bytes to write.
position
refers to the offset from the beginning of the file where this data
should be written. If typeof position !== 'number'
, the data will be written
at the current position. See pwrite(2)
.
The callback will be given three arguments (err, bytesWritten, buffer)
wherebytesWritten
specifies how many bytes were written from buffer
.
If this method is invoked as its util.promisify()
ed version, it returns
a promise for an Object
with bytesWritten
and buffer
properties.
It is unsafe to use fs.write()
multiple times on the same file without waiting
for the callback.
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.
v0.0.67
Asynchronously writes buffer
to the file referenced by the supplied file descriptor.
A file descriptor.
The part of the buffer to be written. If not supplied, defaults to 0
.
The number of bytes to write. If not supplied, defaults to buffer.length - offset
.
Asynchronously writes buffer
to the file referenced by the supplied file descriptor.
A file descriptor.
The part of the buffer to be written. If not supplied, defaults to 0
.
Asynchronously writes buffer
to the file referenced by the supplied file descriptor.
A file descriptor.
Asynchronously writes string
to the file referenced by the supplied file descriptor.
A file descriptor.
A string to write.
The offset from the beginning of the file where this data should be written. If not supplied, defaults to the current position.
The expected string encoding.
Asynchronously writes string
to the file referenced by the supplied file descriptor.
A file descriptor.
A string to write.
The offset from the beginning of the file where this data should be written. If not supplied, defaults to the current position.
Asynchronously writes string
to the file referenced by the supplied file descriptor.
A file descriptor.
A string to write.
Generated using TypeDoc
Write
buffer
to the file specified byfd
. Ifbuffer
is a normal object, it must have an owntoString
function property.offset
determines the part of the buffer to be written, andlength
is an integer specifying the number of bytes to write.position
refers to the offset from the beginning of the file where this data should be written. Iftypeof position !== 'number'
, the data will be written at the current position. Seepwrite(2)
.The callback will be given three arguments
(err, bytesWritten, buffer)
wherebytesWritten
specifies how many bytes were written frombuffer
.If this method is invoked as its
util.promisify()
ed version, it returns a promise for anObject
withbytesWritten
andbuffer
properties.It is unsafe to use
fs.write()
multiple times on the same file without waiting for the callback.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.
Since
v0.0.67