fix: async-mutex not exclusively locking correectly

Jacky Zhao

2023-08-21 b69556c918e2a4a27b047e8de6b02861f04d5a9e

 package-lock.json

@@ -1,17 +1,18 @@
{
  "name": "@jackyzha0/quartz",
  "version": "4.0.7",
  "version": "4.0.8",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "name": "@jackyzha0/quartz",
      "version": "4.0.7",
      "version": "4.0.8",
      "license": "MIT",
      "dependencies": {
        "@clack/prompts": "^0.6.3",
        "@floating-ui/dom": "^1.4.0",
        "@napi-rs/simple-git": "^0.1.8",
        "async-mutex": "^0.4.0",
        "chalk": "^4.1.2",
        "chokidar": "^3.5.3",
        "cli-spinner": "^0.2.10",
@@ -80,6 +81,9 @@
        "prettier": "^3.0.0",
        "tsx": "^3.12.7",
        "typescript": "^5.0.4"
      },
      "engines": {
        "node": ">=18.14"
      }
    },
    "node_modules/@clack/core": {
@@ -1625,6 +1629,14 @@
        "url": "https://github.com/sponsors/wooorm"
      }
    },
    "node_modules/async-mutex": {
      "version": "0.4.0",
      "resolved": "https://registry.npmjs.org/async-mutex/-/async-mutex-0.4.0.tgz",
      "integrity": "sha512-eJFZ1YhRR8UN8eBLoNzcDPcy/jqjsg6I1AP+KvWQX80BqOSW1oJPJXDylPUEeMr2ZQvHgnQ//Lp6f3RQ1zI7HA==",
      "dependencies": {
        "tslib": "^2.4.0"
      }
    },
    "node_modules/asynckit": {
      "version": "0.4.0",
      "resolved": "https://registry.npmjs.org/asynckit/-/asynckit-0.4.0.tgz",
@@ -5579,6 +5591,11 @@
        "url": "https://github.com/sponsors/wooorm"
      }
    },
    "node_modules/tslib": {
      "version": "2.6.2",
      "resolved": "https://registry.npmjs.org/tslib/-/tslib-2.6.2.tgz",
      "integrity": "sha512-AEYxH93jGFPn/a2iVAwW87VuUIkR1FVUKB77NwMF7nBTDkDrrT/Hpt/IrCJ0QXhW27jTBDcf5ZY7w6RiqTMw2Q=="
    },
    "node_modules/tsx": {
      "version": "3.12.7",
      "resolved": "https://registry.npmjs.org/tsx/-/tsx-3.12.7.tgz",