chore(root): update deps

docs/introduction.md

@@ -56,8 +56,8 @@ If you are unsure how to start a project, please refer to the [Quick Start](./qu
 
 For beginners in programming or frontend developers, getting started with game script development using `Pawn`, a procedural language similar to `C`, can be challenging. Additionally, performing basic low-level operations in `Pawn`, such as string concatenation, deletion, and array manipulation, is more cumbersome compared to object-oriented `JavaScript`.
 
-Furthermore, implementing asynchronous functionality is quite difficult within the `Pawn` language ecosystem. Internationalization is typically achieved using `UTF-8` encoding, but since the release of `sa` was quite early, it did not utilize `UTF-8` for internationalization. Instead, it relied on different character sets based on the `ANSI` of the Windows system, such as `ISO-8859-1` in Western countries and `GBK` encoding in China.
+Furthermore, implementing asynchronous functionality is quite difficult within the `Pawn` language ecosystem. Internationalization is typically achieved using `UTF-8` encoding, but since the release of `sa` was quite early, it did not utilize `UTF-8` for internationalization. Instead, it relied on different charsets based on the `ANSI` of the Windows system, such as `ISO-8859-1` in Western countries and `GBK` encoding in China.
 
-Developing localized scripts in `Pawn` often requires setting the file encoding to match the localized Windows system language character set. This can lead to unforeseen encoding issues, such as storing `GBK` data in a `UTF-8` database, which may result in garbled data if not handled properly.
+Developing localized scripts in `Pawn` often requires setting the file encoding to match the localized Windows system language charset. This can lead to unforeseen encoding issues, such as storing `GBK` data in a `UTF-8` database, which may result in garbled data if not handled properly.
 
 By using `JavaScript` for development, we can leverage the power of the `Node.js` ecosystem, including libraries for date and time processing (e.g., `dayjs`), databases (e.g., `MySQL`, `Redis`, `MongoDB`), and asynchronous programming (e.g., `Promises, Async/await`). This allows us to replace `Pawn` ecosystem libraries with equivalent ones from the `Node.js` ecosystem.

package.json

@@ -27,34 +27,34 @@
     "@infernus/streamer": "workspace:^",
     "iconv-lite": "^0.6.3",
     "lodash-unified": "^1.0.3",
-    "pino": "^8.18.0"
+    "pino": "^8.21.0"
   },
   "devDependencies": {
     "@commitlint/cli": "^18.6.1",
-    "@commitlint/config-conventional": "^18.6.2",
+    "@commitlint/config-conventional": "^18.6.3",
     "@rollup/plugin-json": "^6.1.0",
     "@sa-mp/node": "^0.2.0",
     "@types/lodash-es": "^4.17.12",
-    "@types/node": "^20.11.17",
-    "@typescript-eslint/eslint-plugin": "^7.0.1",
-    "@typescript-eslint/parser": "^7.0.1",
+    "@types/node": "^20.12.11",
+    "@typescript-eslint/eslint-plugin": "^7.8.0",
+    "@typescript-eslint/parser": "^7.8.0",
     "all-contributors-cli": "^6.26.1",
-    "bumpp": "^9.3.0",
+    "bumpp": "^9.4.1",
     "conventional-changelog-cli": "^4.1.0",
-    "esbuild": "^0.20.0",
-    "eslint": "^8.56.0",
+    "esbuild": "^0.20.2",
+    "eslint": "^8.57.0",
     "execa": "^8.0.1",
     "husky": "^9.0.11",
-    "inquirer": "^9.2.14",
+    "inquirer": "^9.2.20",
     "lint-staged": "^15.2.2",
     "prettier": "^3.2.5",
-    "rollup": "^4.11.0",
+    "rollup": "^4.17.2",
     "rollup-plugin-delete": "^2.0.0",
     "rollup-plugin-dts": "^6.1.0",
     "rollup-plugin-esbuild": "^6.1.1",
-    "rollup-plugin-node-externals": "^7.0.1",
+    "rollup-plugin-node-externals": "^7.1.2",
     "rollup-plugin-typescript-paths": "^1.5.0",
-    "typescript": "^5.3.3",
-    "vitepress": "^1.0.0-rc.42"
+    "typescript": "^5.4.5",
+    "vitepress": "^1.1.4"
   }
 }