pg-connection-string v2.8.0 broke default export

[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:

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';

Originally posted by @ThisIsMissEm in #3421

[hjr3]

looking at pg-connection-string@2.7.0...pg-connection-string@2.8.0 i wonder if 940479b caused an issue

[cdco-paul-legrand]

+1, had the same issue this morning

[brianc]

+1, had the same issue this morning

so sorry! Publishing a fix right now

[cdco-paul-legrand]

@brianc thanks for such a quick fix 🙌🙌 that was awesome! I hadn't expected to hear back, much less so soon

[brianc]

❤ thanks for letting me know! I always try to do a release in the morning so I can be extra vigilant on monitoring my github issues for the first day just incase something like this happens! I've been on the receiving end of unintended (and also semver major) breaking changes enough to know the pain, and I want to reduce that pain for as many folks as possible.