@@ -704,7 +704,7 @@ changes:
704
704
* Returns: {Promise}
705
705
706
706
Asynchronously writes data to a file, replacing the file if it already exists.
707
- ` data` can be a string, a buffer, an {AsyncIterable} or {Iterable} object.
707
+ ` data` can be a string, a buffer, an {AsyncIterable}, or an {Iterable} object.
708
708
The promise is resolved with no arguments upon success.
709
709
710
710
If ` options` is a string, then it specifies the ` encoding` .
@@ -1684,7 +1684,7 @@ access(file, constants.R_OK | constants.W_OK, (err) => {
1684
1684
```
1685
1685
1686
1686
Do not use `fs.access()` to check for the accessibility of a file before calling
1687
- `fs.open()`, `fs.readFile()` or `fs.writeFile()`. Doing
1687
+ `fs.open()`, `fs.readFile()`, or `fs.writeFile()`. Doing
1688
1688
so introduces a race condition, since other processes may change the file's
1689
1689
state between the two calls. Instead, user code should open/read/write the
1690
1690
file directly and handle the error raised if the file is not accessible.
@@ -2409,7 +2409,7 @@ has only one boolean parameter. This is one reason `fs.access()` is recommended
2409
2409
instead of `fs.exists()`.
2410
2410
2411
2411
Using `fs.exists()` to check for the existence of a file before calling
2412
- `fs.open()`, `fs.readFile()` or `fs.writeFile()` is not recommended. Doing
2412
+ `fs.open()`, `fs.readFile()`, or `fs.writeFile()` is not recommended. Doing
2413
2413
so introduces a race condition, since other processes may change the file's
2414
2414
state between the two calls. Instead, user code should open/read/write the
2415
2415
file directly and handle the error raised if the file does not exist.
@@ -3873,7 +3873,7 @@ Asynchronous stat(2). The callback gets two arguments `(err, stats)` where
3873
3873
In case of an error, the ` err.code` will be one of [Common System Errors][].
3874
3874
3875
3875
Using ` fs.stat()` to check for the existence of a file before calling
3876
- ` fs.open()` , ` fs.readFile()` or ` fs.writeFile()` is not recommended.
3876
+ ` fs.open()` , ` fs.readFile()` , or ` fs.writeFile()` is not recommended.
3877
3877
Instead, user code should open/ read/ write the file directly and handle the
3878
3878
error raised if the file is not available.
3879
3879
@@ -6363,7 +6363,7 @@ changes:
6363
6363
6364
6364
A {fs.Stats} object provides information about a file.
6365
6365
6366
- Objects returned from [` fs .stat ()` ][], [` fs .lstat ()` ][] and [` fs .fstat ()` ][] and
6366
+ Objects returned from [` fs .stat ()` ][], [` fs .lstat ()` ][], [` fs .fstat ()` ][], and
6367
6367
their synchronous counterparts are of this type.
6368
6368
If ` bigint` in the ` options` passed to those methods is true, the numeric values
6369
6369
will be ` bigint` instead of ` number` , and the object will contain additional
@@ -7521,7 +7521,7 @@ fs.open('<directory>', 'a+', (err, fd) => {
7521
7521
` ` `
7522
7522
7523
7523
On Windows, opening an existing hidden file using the ` ' w' ` flag (either
7524
- through ` fs .open ()` or ` fs .writeFile ()` or ` fsPromises .open ()` ) will fail with
7524
+ through ` fs .open ()` , ` fs .writeFile ()` , or ` fsPromises .open ()` ) will fail with
7525
7525
` EPERM ` . Existing hidden files can be opened for writing with the ` ' r+' ` flag.
7526
7526
7527
7527
A call to ` fs .ftruncate ()` or ` filehandle .truncate ()` can be used to reset
0 commit comments