chore: updated packages

.deploy.config.js

@@ -1,5 +1,5 @@
 export default {
-    fxserverPath: 'E:\\FiveM\\6461\\fxserver.exe',
+    fxserverPath: 'E:\\FiveM\\6520\\fxserver.exe',
     debouncerInterval: 250,
     preReleaseExpirationDays: 21,
     txAdminArgs: [

.npm-upgrade.json

@@ -15,6 +15,10 @@
     "windows-release": {
       "versions": ">4",
       "reason": "inlined to transform it into async"
+    },
+    "@types/node": {
+      "versions": ">16.9.1",
+      "reason": "fixed to fxserver's node version"
     }
   }
 }

core/globalData.ts

@@ -60,6 +60,7 @@ const resourceName = GetCurrentResourceName();
 //4574 = add resource field to PRINT_STRUCTURED_TRACE
 //5894 = CREATE_VEHICLE_SERVER_SETTER
 //6185 = added ScanResourceRoot (not yet in use)
+//6508 = unhandledRejection is now handlable, we need this due to discord.js's bug
 const minFXServerVersion = 5894;
 const fxServerVersion = getBuild(getConvarString('version'));
 if (fxServerVersion === 9999) {

core/index.ts

@@ -52,7 +52,6 @@ process.stdout.on('error', (data) => { });
 process.stderr.on('error', (data) => { });
 
 //Handle "the unexpected"
-//FIXME: this one literally doesn't work due to how fxserver handles them
 process.on('unhandledRejection', (err: Error) => {
     console.error('Ohh nooooo - unhandledRejection');
     console.dir(err);
@@ -68,6 +67,9 @@ process.on('exit', (_code) => {
 Error.stackTraceLimit = 25;
 process.removeAllListeners('warning');
 process.on('warning', (warning) => {
+    //totally ignoring the warning, we know this is bad and shouldn't happen
+    if (warning.name === 'UnhandledPromiseRejectionWarning') return;
+
     if (warning.name !== 'ExperimentalWarning' || convars.isDevMode) {
         console.dir(warning);
     }