pg-connection-string version 3.0.0

[hjr3]

Roadmap for the 3.0.0 version of pg-connection-string

Proposed changes:

• use libpq semantics for sslmode
  • remove no-verify option
• only accept libpq compatible query parameters
  • Querystring in connection string #1095
• support multiple hosts to conform with libpq
  • Connection String with multiple hosts is not being parsed as expected #2308
  • Support for multiple hosts #1470
• be more strict in what query param values are accepted
  • Fix parsing of ssl=false connection string parameter #2423
• fix the pg surprise where the entire ssl configuration is replaced if SSL-related options exist in connectionString
  • Usage of ?sslmode=require and ssl property in pg.Pool #3355
  • feat: allow all config options when using connection string and object #3327
  • SSL settings are not deep merged with params parsed from connectionString #2380
• make parse compatible with ConnectionOptions by default
  • see ConnectionOptions interface is incompatible with @types/pg definitions #2637

Related discussions:

• fix(pg-connection-string): get closer to libpq semantics for sslmode #2709

[ThisIsMissEm]

@hjr3 just a heads up, 2.8.0 was technically a breaking change. Even though module.exports = parse still existed, it broke the default export:

import pgConnectionString from 'pg-connection-string';
       ^^^^^^^^^^^^^^^^^^
SyntaxError: The requested module 'pg-connection-string' does not provide an export named 'default'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:180:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:263:5)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:578:26)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:116:5)

Node.js v22.14.0

I'm guessing it's an ESM / bundler or whatever type error, but it's easy enough to fix and switch to import { parse } from 'pg-connection-string';

[hjr3]

@hjr3 just a heads up, 2.8.0 was technically a breaking change. Even though module.exports = parse still existed, it broke the default export:

i opened #3424 and will triage there

[brianc]

i opened #3424 and will triage there

thanks! Sorry 'bout that. Published a patch version which contains the fix for the default export.

[ThisIsMissEm]

Cool & no worries, we picked up the issue pretty quickly on the mastodon side