@matrixai/async-init
Advanced tools
Comparing version 1.8.3 to 1.8.4
{ | ||
"name": "@matrixai/async-init", | ||
"version": "1.8.3", | ||
"version": "1.8.4", | ||
"author": "Roger Qiu", | ||
@@ -25,3 +25,3 @@ "description": "Asynchronous Initialisation and Deinitialisation Decorators", | ||
"dependencies": { | ||
"@matrixai/async-locks": "^3.2.0", | ||
"@matrixai/async-locks": "^4.0.0", | ||
"@matrixai/errors": "^1.1.7" | ||
@@ -33,3 +33,3 @@ }, | ||
"@types/jest": "^28.1.3", | ||
"@types/node": "^18.11.11", | ||
"@types/node": "^18.15.0", | ||
"@typescript-eslint/eslint-plugin": "^5.45.1", | ||
@@ -36,0 +36,0 @@ "@typescript-eslint/parser": "^5.45.1", |
@@ -94,3 +94,3 @@ # js-async-init | ||
The `start`, `stop`, and `destroy` calls are all concurrent-controlled with `RWLock`. They are idempotent and they are mutually exclusive between each other and any blocking `ready` decorated methods. Decorated methods can block `start`, `stop`, and `destroy`, but share a read lock between each other. | ||
The `start`, `stop`, and `destroy` calls are all concurrent-controlled with `RWLockWriter`. They are idempotent and they are mutually exclusive between each other and any blocking `ready` decorated methods. Decorated methods can block `start`, `stop`, and `destroy`, but share a read lock between each other. | ||
@@ -97,0 +97,0 @@ Refer to https://gist.github.com/CMCDragonkai/1dbf5069d9efc11585c27cc774271584 for further the motivation of this library. |
68248
+ Added@matrixai/async-cancellable@1.1.1(transitive)
+ Added@matrixai/async-locks@4.0.0(transitive)
+ Added@matrixai/timer@1.1.3(transitive)
- Removed@matrixai/async-locks@3.2.0(transitive)
- Removedasync-mutex@0.3.2(transitive)
- Removedtslib@2.8.1(transitive)
Updated@matrixai/async-locks@^4.0.0