Hi all, is anyone using pact-js v9.18.1 with custo...
# pact-jsn
Nick Meyer
10/07/2022, 4:06 PMHi all, is anyone using pact-js v9.18.1 with custom binaries? I’m trying to use the straight ruby gems instead of the standalone binaries to workaround the architecture limitations with travelling Ruby (yes, I know v10 uses the new Rust standalone, there are other things preventing us from making that change at the moment). I use
PACT_SKIP_BINARY_INSTALL=truepact_binary_locationNPM_CONFIG_PACT_BINARY_LOCATIONt
Timothy Jones
10/08/2022, 11:14 AMI… don’t think this will work
Timothy Jones
10/08/2022, 11:14 AMIt needs the binaries, which are made with travelling Ruby
Timothy Jones
10/08/2022, 11:15 AMI don’t think there’s a way to get these binaries directly with the gems
Timothy Jones
10/08/2022, 11:15 AMbut hey, I know the answer to your question
Timothy Jones
10/08/2022, 11:16 AMNPM_CONFIG_PACT_BINARY_LOCATION^ This gives pact a custom location to download the binaries from
PACT_SKIP_BINARY_INSTALL=true^ This tells pact not to download the binaries. Don’t set it if you want to provide custom binaries.
Timothy Jones
10/08/2022, 11:16 AMLet us know if you get it working!
Timothy Jones
10/08/2022, 11:18 AManyone using pact-js v9.18.1 with custom binaries?I’m not a maintainer any more, but I’ve not heard of anyone trying this
m
Matt (pactflow.io / pact-js / pact-go)
10/08/2022, 10:29 PM
Yes we don't support this Nick, but we could.
Given it's the old 9.x.x line, we're not actively investing in new features but would happily accept a PR for it
Matt (pactflow.io / pact-js / pact-go)
10/08/2022, 10:29 PM
The issue is the current config option supports a custom location of the compressed archive, but paths to the binaries. We could potentially make it discover the binaries elsewhere
n
Nick Meyer
10/08/2022, 10:33 PMThanks for responding folks. I was able to work around it by jerry-rigging our Dockerfiles to link the scripts installed by the gem into the expected location after npm install, that will work for now. We’re evaluating moving to v10 but we are trying to keep the tooling consistent across our stack and we aren’t quite comfortable enough just yet to pull the trigger on moving to v2 on our Go apps.
👍 1
Nick Meyer
10/08/2022, 10:35 PMThe other alternative I looked at was packaging up those same scripts similar to how the stand-alone are packaged and then using the config option, but this ultimately got us there faster and without having to create a new artifact.
👍 2
t
Timothy Jones
10/09/2022, 6:06 AMYou should be able to generate the older pact version with pact-js v10
☝️ 1