Replies: 2 comments 2 replies
-
I like option 2, but I would also say that we should move the ruby parts into |
Beta Was this translation helpful? Give feedback.
2 replies
-
done as part of #488 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
👋 hello Pact JS-ers.
We have an issue at the moment (#416).
The TL;DR is that we package the Ruby standalone into the
pact-core
package, which is a dependency forpact
to work, and these ruby binaries only work on a subset of OSs now, whereas we support a broader set in Pact JS (notably, arm/aarch64).This means that the package can only be run on the lowest common denominator OS/arch combinations, causing issues such as #416
I’m proposing one of two things:
Option 1
Pros
pact
(the thing 99% of our users actually need)pact-core
if they still want to get the bundled Ruby CLICons
Option 2
Pros
Cons
Beta Was this translation helpful? Give feedback.
All reactions