Closed gigamac closed 2 months ago
Switch to pact-cli has resolved this, but what has actually happened,?
the cli tools were removed in pact-js 13.x and migrated into pact-cli. breaking changes noted in release notes
https://github.com/pact-foundation/pact-js/releases/tag/v13.0.0
thanks - not sure why but the same command in gitlab using pact-foundation/pact is working today, but clearly we should be using pact-cli - much appreciated
Yeah that is a bit odd, maybe there was some caching involved., sorry it impacted you!
I noticed this error
$ npm ci --cache .npm --prefer-offline
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated read-pkg-up@11.0.0: Renamed to read-package-up
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error <https://github.com/npm/cli/issues>
npm error A complete log of this run can be found in: /builds/clickclickgo/project101/.npm/_logs/2024-07-19T13_22_57_186Z-debug-0.log
which actually prevents npm install from completing and was fixed in the latest 22.4.x of node. there was a bug in 22.4.0 or 1 from memory
Hi,
I am seeing this in a pipeline job for unit tests today, when it has ben a stable job for a number of months:
npm ERR! 404 Not Found - GET https://registry.npmjs.org/pact-broker - Not found
this is both running against an internal artifactory repo, and against the node registry (as above) I also tried this independently in my own gitlab.com pipeline tat i use for debugsings. package json:
yml: