/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
file:///home/overitis19/public_html/greatmiracle19/dist/index.mjs:96996
  throw new Error(
        ^

Error: AI_INTEGRATIONS_GEMINI_BASE_URL must be set. Did you forget to provision the Gemini AI integration?
    at file:///home/overitis19/public_html/greatmiracle19/dist/index.mjs:96996:9
    at ModuleJob.run (node:internal/modules/esm/module_job:343:25)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:681:26)

Node.js v22.22.3
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
file:///home/overitis19/public_html/greatmiracle19/dist/index.mjs:96996
  throw new Error(
        ^

Error: AI_INTEGRATIONS_GEMINI_BASE_URL must be set. Did you forget to provision the Gemini AI integration?
    at file:///home/overitis19/public_html/greatmiracle19/dist/index.mjs:96996:9
    at ModuleJob.run (node:internal/modules/esm/module_job:343:25)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:681:26)

Node.js v22.22.3
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
file:///home/overitis19/public_html/greatmiracle19/dist/index.mjs:96996
  throw new Error(
        ^

Error: AI_INTEGRATIONS_GEMINI_BASE_URL must be set. Did you forget to provision the Gemini AI integration?
    at file:///home/overitis19/public_html/greatmiracle19/dist/index.mjs:96996:9
    at ModuleJob.run (node:internal/modules/esm/module_job:343:25)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:681:26)

Node.js v22.22.3
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
file:///home/overitis19/public_html/greatmiracle19/dist/index.mjs:96996
  throw new Error(
        ^

Error: AI_INTEGRATIONS_GEMINI_BASE_URL must be set. Did you forget to provision the Gemini AI integration?
    at file:///home/overitis19/public_html/greatmiracle19/dist/index.mjs:96996:9
    at ModuleJob.run (node:internal/modules/esm/module_job:343:25)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:681:26)

Node.js v22.22.3
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:4154490) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:4162852) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:4163518) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:4163803) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:6581) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:832147) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:833159) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:836327) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:836636) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:839411) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:842638) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:842958) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:883883) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:933288) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:933411) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:1385828) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:1387233) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:1391207) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=postgresql://neondb_owner:npg_w9AC7dZKHoLW@ep-shy-poetry-atw76urg.c-9.us-east-1.aws.neon.tech/neondb?sslmode=require': not a valid identifier
/home/overitis19/nodevenv/public_html/greatmiracle19/22/bin/node: line 10: export: `=/home/overitis19/public_html/greatmiracle19/public': not a valid identifier
(node:1432347) Warning: SECURITY WARNING: The SSL modes 'prefer', 'require', and 'verify-ca' are treated as aliases for 'verify-full'.
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 guarantees.

To prepare for this change:
- If you want the current behavior, explicitly use 'sslmode=verify-full'
- If you want libpq compatibility now, use 'uselibpqcompat=true&sslmode=require'

See https://www.postgresql.org/docs/current/libpq-ssl.html for libpq SSL mode definitions.
(Use `node --trace-warnings ...` to show where the warning was created)