Hi there My organisation is still using pact-node (v10.9.4) as well as pact js (v9.11.0) as part of a contract testing library for our microservices and I'm thinking since https://www.npmjs.com/package/@pact-foundation/pact-node#which-librarypackage-should-i-use states that pact-js includes pact-nodes ability to publish to the pact broker I should be able to remove the pact-node dependency without any issue yes? I'm looking to upgrade our pacts from v2 to v3. I'm assuming I'll also need to be weary of the fact the microservices are being ran on alpine and also that some of the consumer contract testing code will need to be updated to the new stuff?

pact-js depends on pact-node. You don’t need to include it unless you’re importing it somewhere.

@Timothy Jones thanks for your reply, what do you mean by unless I'm importing it somewhere? Would you be able to describe an example? At the moment in the package.json of our contract testing library there is pact-foundation/pact-node and pact-foundation/pact so I'm assuming you mean that since pact-js already depends on pact-node then I can just remove pact-node from the package.json since pact-node will already be in the package.json of the pact-foundation/pact package that's being installed in our contract testing library?

yes, this is fine, unless you have an

import

or a

require

somewhere that explicitly mentions

pact-node

The runtime of your application shouldn't impact pact tests that run locally. But note we don't support running tests on alpine itself