'log' does not exist in type 'PactV3Options'

[stevenKirill]

Software versions

• OS: _e.g. Mac Ventura OSX 13.2.1 (22D68)
• Consumer Pact library:"@pact-foundation/pact": "^11.0.2",
• Provider Pact library: "@pact-foundation/pact": "^11.0.2",
• Node Version: 18

Issue Checklist

Please confirm the following:

• [x] I have upgraded to the latest
• [x] I have the read the FAQs in the Readme
• [x] I have triple checked, that there are no unhandled promises in my code and have read the section on intermittent test failures
• [x] I have set my log level to debug and attached a log file showing the complete request/response cycle
• [x] For bonus points and virtual high fives, I have created a reproduceable git repository (see below) to illustrate the problem

Expected behaviour

correct type fot log property

Actual behaviour

log doesn't exist

Steps to reproduce

export const provider = new PactV3({ consumer: 'gpb-expert-consumer', provider: 'gpb-expert-provider', logLevel: 'info', log: path.resolve(process.cwd(), 'logs', 'pact.log'), dir: path.resolve(process.cwd(), 'pacts'), spec: SpecificationVersion.SPECIFICATION_VERSION_V2, });

Relevan

t log files

[mefellows]

Yes, Log doesn't exist on that type. Have we documented it somewhere that we have?

[mefellows]

There is an open feature request for logging to file here: #954. Closing this (unless it's a different big/feature, please reopen and clarify if that's the case).

[TimothyJones]

The missing log parameter isn't mentioned in the migration instructions.

It looks like the migration instructions aren't a distillation of the notes on breaking changes - for example, the verifier instructions say no changes required, but there were actually several changes to the options detailed here

[mefellows]

Yes that's a good point, i'll raise a separate tracking issue for that now.