Skip to content

Commit 976d0f8

Browse files
mcollinaaduh95
andauthored
Apply suggestions from code review
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
1 parent 630eb58 commit 976d0f8

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

doc/api/single-executable-applications.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -178,10 +178,14 @@ See documentation of the [`sea.getAsset()`][], [`sea.getAssetAsBlob()`][],
178178

179179
### Virtual File System (VFS) for assets
180180

181+
<!-- YAML
182+
added: REPLACEME
183+
-->
184+
181185
> Stability: 1 - Experimental
182186
183187
In addition to using the `node:sea` API to access individual assets, you can use
184-
the Virtual File System (VFS) to access bundled assets through standard `fs`
188+
the Virtual File System (VFS) to access bundled assets through standard `node:fs`
185189
APIs. To enable VFS, set `"useVfs": true` in the SEA configuration. When
186190
enabled, the VFS is automatically initialized and mounted at `/sea`. All
187191
assets defined in the SEA configuration are accessible through this virtual
@@ -205,7 +209,7 @@ if (fs.existsSync('/sea/optional.json')) {
205209
}
206210
```
207211

208-
The VFS supports all common `fs` operations for reading files and directories.
212+
The VFS supports all common `node:fs` operations for reading files and directories.
209213
Since the SEA VFS is read-only, write operations are not supported. See the
210214
[VFS documentation][] for the full list of supported and unsupported operations.
211215

0 commit comments

Comments
 (0)