async-file-tried 1.2.5 → 1.2.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -0
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -22,6 +22,9 @@ Import:
|
|
|
22
22
|
import fs from 'async-file-tried';
|
|
23
23
|
```
|
|
24
24
|
|
|
25
|
+
[](https://www.slanted.de/product/what-was-design/)
|
|
26
|
+
|
|
27
|
+
|
|
25
28
|
## Usage
|
|
26
29
|
|
|
27
30
|
Usually we do not want to make calls against the file system without a proper error handling. But the try-catch block is somewhat unelegant because it moves code blocks in the bracket sub-space and thus disturbs the linearity of our programming. *async-file-tried* returns a tuple with either the response or the error from a fs call and simplifies error handling.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "async-file-tried",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.6",
|
|
4
4
|
"description": "A try-catch wrapper around node’s fs/promises.",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"types": "dist/index.d.ts",
|
|
@@ -21,10 +21,10 @@
|
|
|
21
21
|
},
|
|
22
22
|
"homepage": "https://github.com/fwalzel/async-file-tried#readme",
|
|
23
23
|
"devDependencies": {
|
|
24
|
-
"@types/node": "^25.3.
|
|
24
|
+
"@types/node": "^25.3.5",
|
|
25
25
|
"c8": "^11.0.0",
|
|
26
26
|
"chai": "^6.2.2",
|
|
27
|
-
"mocha": "^11.
|
|
27
|
+
"mocha": "^11.7.5",
|
|
28
28
|
"typescript": "^5.9.3"
|
|
29
29
|
},
|
|
30
30
|
"keywords": [
|