#47 fix: add peer dep pact-js v11 and nest-js v10 Pull request opened by JoffrayBillon Add Nest 10 and Pact 11 support Description As there is no impacting changes with the Nest 10 and Pact 11 releases for this package change the peerDependencies, to allow nest 10 to be used as a peer dependancy. Also changed the fixed v10 pact version to any v10 and v11 (ok for v11 as I said before) Motivation and Context Make the package work for NestJS recent release 10 on

npm install

without error

Conflicting peer dependency

. How Has This Been Tested? In my fork branch of the

nestjs-pact

project:

npm run build
npm pack --pack-destination ~

Then in the "final project" I try

npm install

after replacing in the `package.json`:

"nestjs-pact": "^2.3.0",

With

"nestjs-pact": "file:~/nestjs-pact-2.3.1.tgz",

Check if installation pass, looks good, good to go. Types of changes ☐ Bug fix (non-breaking change which fixes an issue) ☑︎ New feature (non-breaking change which adds functionality) ☐ Breaking change (fix or feature that would cause existing functionality to change) Checklist: ☐ My change requires a change to the documentation. ☐ I have updated the documentation accordingly. ☐ I have added tests to cover my changes. ☑︎ All new and existing tests passed. pact-foundation/nestjs-pact GitHub Actions: Build & Test (18.x) GitHub Actions: Build & Test (16.x) GitHub Actions: Build & Test (14.x) ✅ 1 other check has passed 1/4 successful checks