👋 Hey folks. Had a quick question and I'm not sure if there's a know GH issue around it or this has been asked previously in slack. We've been running into an issue with spinning up the mock provider at runtime when using node 18:

connect ECONNREFUSED ::1:8080

Making a switch back to 16 works. Curious if there's been a solution to this or path forward? We're looking to start running things in CI and wondering if we'd have to pull down a specific node docker container when running pact tests.

It’s to do with networking changes in Node 18+

Ah copy that. Thanks Matt. Let me try manually setting the host.

There's also a change to the way that connection pooling works. The details are in the node release notes, and also on an issue in github I think

Thanks, I meant to send that link but clearly I got side tracked

FWIW - I did come across the relevant Pact GH issues: • https://github.com/pact-foundation/pact-js/discussions/1083 • https://github.com/pact-foundation/pact-js/issues/1066 I changed refs to

localhost

to

127.0.0.1

but to no avail:

const provider = new Pact({
    consumer: consumerName,
    provider: providerName,
    host: '127.0.0.1',
    port: 8080,
    log: path.resolve(process.cwd(), 'logs', 'pact.log'),
    dir: pactDir,
});

I'm also on

arm64

if that helps