fix wording in asar doc
This commit is contained in:
parent
99ec841a8e
commit
3a9c57231e
1 changed files with 2 additions and 2 deletions
|
@ -95,7 +95,7 @@ $.get('file:///path/to/example.asar/file.txt', (data) => {
|
||||||
### Treating an `asar` Archive as a Normal File
|
### Treating an `asar` Archive as a Normal File
|
||||||
|
|
||||||
For some cases like verifying the `asar` archive's checksum, we need to read the
|
For some cases like verifying the `asar` archive's checksum, we need to read the
|
||||||
content of `asar` archive as file. For this purpose you can use the built-in
|
content of an `asar` archive as a file. For this purpose you can use the built-in
|
||||||
`original-fs` module which provides original `fs` APIs without `asar` support:
|
`original-fs` module which provides original `fs` APIs without `asar` support:
|
||||||
|
|
||||||
```javascript
|
```javascript
|
||||||
|
@ -111,7 +111,7 @@ process.noAsar = true;
|
||||||
fs.readFileSync('/path/to/example.asar');
|
fs.readFileSync('/path/to/example.asar');
|
||||||
```
|
```
|
||||||
|
|
||||||
## Limitations on Node API
|
## Limitations of the Node API
|
||||||
|
|
||||||
Even though we tried hard to make `asar` archives in the Node API work like
|
Even though we tried hard to make `asar` archives in the Node API work like
|
||||||
directories as much as possible, there are still limitations due to the
|
directories as much as possible, there are still limitations due to the
|
||||||
|
|
Loading…
Reference in a new issue