fix: add deprecation warnings for pact cli tools in pact-js-core #514
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Inform users of upcoming breaking change in #513
Considerations
Users may be setup to output in json format. This warning will appear conditionally I believe, so may mess up workflows if one if using the json output from stdout and now has a warning in it.
An option to silence the warnings is provided if
PACT_SILENCE_DEPRECATION_WARNINGS
is set totrue
Breaking change detail
All CLI/API functionality provided by the Pact CLI tools (ruby based) will be moved in pact-js-core 15.x to pact-js-cli.
Repo
NPM Package
imports
@pact-foundation/pact-core
imports will now become@pact-foundation/pact-cli
for programatic usage of the CLI toolsnpx usage
npx --package=@pact-foundation/pact-cli@15.0.1 -c pact-broker