-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PACT CRASHED #524
Comments
@mefellows @YOU54F could you please look into it? |
Please provide a repro |
@mefellows I've large codebase in which this issue is occurring. creating repository will take time. in the message it mentioned to report so I reported it. |
Thanks, we don't need your actual code just some code that reproduces the error. The migration from 9-10 was a significant change. P.a. you need not tag maintainers, we already subscribe to all issues. |
Got it. I'm trying to create repo. I'll share here once ready.
Okay. thank you. |
☝🏾 in the new issue template I'll be honest and say nestjs-pact has stalled in terms of development, and I'm personally spread over too many things to be massively driven to do anything about it, so we would either ask for contributions to fix it, or suggest migrating to using pact-js directly. |
creating repo will take time for me maybe I can do it over weekend but for now I've created Gist. Let me know if you need anything else. |
I added some previous examples https://github.com/YOU54F/nestjs-pact-test?tab=readme-ov-file#pact-js-v10 off the back of |
this one was helpful. thank you @YOU54F |
Thanks Yousaf! |
I removed |
Does this mean your issue is fixed? If so, this ticket can be closed. |
Yes, it's working. I'm closing it thank you everyone. |
Software versions
Some more information
nestjs-pact
library with version: 2.3.1nestjs-pact
from v2.2.1 to v.2.3.1 and@pact-foundation/pact
from v.9.18.1 to v.10.4.0I'm getting below errors:
The text was updated successfully, but these errors were encountered: