Hey everyone! I just encountered this error with the most recent version (4 hours ago) of pact-node 10.17.5:

$ yarn add @pact-foundation/pact-node@10.17.5
yarn add v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
error /tmp/tmp.CovE6vLZ5q/node_modules/@pact-foundation/pact-node: Command failed.
Exit code: 1
Command: node postinstall.js
Arguments: 
Directory: /tmp/tmp.CovE6vLZ5q/node_modules/@pact-foundation/pact-node
Output:
Installing Pact Standalone Binary for linux.
Downloading Pact Standalone Binary v1.89.02-rc1 for platform linux from <https://github.com/pact-foundation/pact-ruby-standalone/releases/download/v1.89.02-rc1/pact-1.89.02-rc1-linux-x86_64.tar.gz>
Please note: we are tracking this download anonymously to gather important usage statistics. To disable tracking, set 'pact_do_not_track: true' in your package.json 'config' section.
Downloaded 26.57%...
Downloaded 84.62%...
Finished downloading binary to /tmp/tmp.CovE6vLZ5q/node_modules/@pact-foundation/pact-node/standalone/pact-1.89.02-rc1-linux-x86_64.tar.gz
Error: Error while installing binary: Postinstalled Failed Unexpectedly: Error: Error while installing binary: Checksum file missing from standalone directory. Aborting.
    at throwError (/tmp/tmp.CovE6vLZ5q/node_modules/@pact-foundation/pact-node/standalone/install.js:42:11)
    at /tmp/tmp.CovE6vLZ5q/node_modules/@pact-foundation/pact-node/standalone/install.js:327:16
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
info Visit <https://yarnpkg.com/en/docs/cli/add> for documentation about this command.

Might be good to know what hardware you're running on, in case it's a xcompiled arch problem

ah, yes I am running on Linux Mint with processor arch x86_64

so, not M1, then yay

nope

yeah,

rc1-linux-x86_64.tar.gz

should've been a giveaway, hiding in the middle there 🙃

I see the checksum in there, I wonder what's going on...

Hmm yeah something funny is going down. Looks like pact-js

npm install @pact-foundation/pact@9.17.3

fails

npm install @pact-foundation/pact@9.17.2

passed Release 9.17.3 https://github.com/pact-foundation/pact-js/releases/tag/v9.17.3 • brings in an update to upgrade to latest pact-node (0d9b127) https://github.com/pact-foundation/pact-js/commit/0d9b1270d4dc03e761941ae060b2a75db0bab24d#diff-7ae45ad102eab3b6d7e789[…]6470d7bc6507b6481575d519R97

"@pact-foundation/pact-node": "^10.17.2",

pact-js-core

released https://github.com/pact-foundation/pact-js-core/releases/tag/v13.6.2 which is on npm as • pact-core - https://www.npmjs.com/package/@pact-foundation/pact-core • pact-node - https://www.npmjs.com/package/@pact-foundation/pact-node which pact-js uses, the latest release is 10.17.5 so will be picked up by the caret in the pact-node dep in pact-js. Looking at the changes in https://github.com/pact-foundation/pact-ruby-standalone/commits/master the latest release brought in an addition of some azure env vars from this issue https://github.com/pact-foundation/pact_broker-client/commit/889f83f3d24dfa4db2824a0049e11ec97a391ab2 so pretty innocuous.

sorry folks, this is fixed now. My guess is that a manual step in this release process (

pact-node

) failed and somebody (me) didn’t notice. We should be back to an automated release process soon - the beta branch is very close to being stable with support for all major features (and some), and I hope to release that in about 2 weeks. This week it’s getting a green build, next week I’m away in the states, and the week after is tidy up, docs, socialising and working with Yousaf and co (assuming all is well, of course).

Working for me now buddy hooray thanks Matt for taking the time this evening and enjoy a nice whiskey after that. Looking forward to catching up in person, helping iron out the kinks over the upcoming months and getting a proper smooth Pact release train, so that we can all kick back and relax like Paxtonpactflow platypus slack

Can’t wait for next week!

Those instructions are not right

Thanks for this everyone, it's working for me now 👍