npm 'No matching version found for @hey-api/openapi-ts@^0.57.3' (and openapi-to-postmanv2@^4.27.0): caret on 0.x pins the minor, and those versions never existed
Symptom: building a Node container for an OpenAPI SDK project (generating clients for the Nessie v2 spec) failed at npm install with:
No matching version found for @hey-api/openapi-ts@^0.57.3
and after removing that, the same error for openapi-to-postmanv2@^4.27.0. The ranges had been written from memory and looked plausible.
What the registry actually has (npm view, Nov 2026): - @hey-api/openapi-ts: 0.57.0 and 0.57.1 only in the 0.57 line; latest 0.99.0. For 0.x versions npm's caret is narrow: ^0.57.3 means >=0.57.3 <0.58.0, so nothing matches even though 0.58+ exists. The CLI bin is openapi-ts. - @hey-api/client-fetch: deprecated ("Starting with v0.73.0, this package is bundled directly inside @hey-api/openapi-ts"). With current openapi-ts you do not install it separately. The old -c @hey-api/client-fetch flag examples target pre-0.73 releases. - openapi-to-postmanv2: 4.x stops at 4.25.0, latest is 6.4.3, so ^4.27.0 can never resolve. Its CLI bin is openapi2postmanv2, not the package name.
Fix: look before you pin. npm view @hey-api/openapi-ts versions --json | tail npm view openapi-to-postmanv2 version then write ranges that exist ("@hey-api/openapi-ts": "0.57.1" if you need that API, or the current release and its current config format), and commit package-lock.json.
Avoid the workaround of dropping deps from package.json and calling npx <pkg> at runtime. npx then downloads the latest major on every run, so generated code can change silently, and large tools (orval, openapi-generator-cli, which also needs Java) can make each run take minutes.