TEST1
4.5(1k)
TEST1 screenshot 1
TEST1 screenshot 2
TEST1 screenshot 3

TEST1 Mods

testtt 03:36:58.723 Running build in Washington, D.C., USA (East) – iad1 03:36:58.723 Build machine configuration: 2 cores, 8 GB 03:36:58.734 Cloning github.com/SOULAIMANEIDBOUFKER/game-mod-hub-main (Branch: main, Commit: e8c61b9) 03:36:58.736 Skipping build cache, deployment was triggered without cache. 03:37:01.946 Cloning completed: 3.211s 03:37:02.516 Running "vercel build" 03:37:03.141 Vercel CLI 50.32.4 03:37:03.883 Installing dependencies... 03:37:06.701 npm warn deprecated whatwg-encoding@2.0.0: Use @exodus/bytes instead for a more spec-conformant and faster implementation 03:37:09.115 npm warn deprecated domexception@4.0.0: Use your platform's native DOMException instead 03:37:41.641 ✓ Compiled successfully in 12.6s 03:37:41.644 Running TypeScript ... 03:37:42.167 Collecting page data using 1 worker ... 03:37:42.745 Generating static pages using 1 worker (0/10) ... 03:37:42.939 (node:368) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'. 03:37:42.940 In the next major version (pg-connection-string v3.0.0 and pg v9.0.0), these modes will adopt standard libpq semantics, which have weaker security

Updated:
Users:1k+
Views:15k
PC

Download Now

Preparing secure download...

About TEST1 Mods

guarantees. 03:37:42.940 03:37:42.940 To prepare for this change: 03:37:42.941 - If you want the current behavior, explicitly use 'sslmode=verify-full' 03:37:42.941 - If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require' 03:37:42.941 03:37:42.941 See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions. 03:37:42.942 (Use node --trace-warnings ... to show where the warning was created) 03:37:43.582 Generating static pages using 1 worker (2/10) guarantees. 03:37:42.940 03:37:42.940 To prepare for this change: 03:37:42.941 - If you want the current behavior, explicitly use 'sslmode=verify-full' 03:37:42.941 - If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require' 03:37:42.941 03:37:42.941 See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions. 03:37:42.942 (Use node --trace-warnings ... to show where the warning was created) 03:37:43.582 Generating static pages using 1 worker (2/10) guarantees. 03:37:42.940 03:37:42.940 To prepare for this change: 03:37:42.941 - If you want the current behavior, explicitly use 'sslmode=verify-full' 03:37:42.941 - If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require' 03:37:42.941 03:37:42.941 See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions. 03:37:42.942 (Use node --trace-warnings ... to show where the warning was created) 03:37:43.582 Generating static pages using 1 worker (2/10)

View all news
More in shooter