Missing peer dependency `ajv` in `better-ajv-errors` causes installation failures

[aklkv]

Describe the bug

When installing @redocly/cli in strict peer dependency environments, the installation fails because better-ajv-errors (a transitive dependency via @redocly/respect-core) declares ajv as a peer dependency, but it's not installed or made available by the parent package. This causes the installation to fail when strictPeerDependencies: true is enabled.

To Reproduce

1. Create a pnpm-workspace.yaml with strictPeerDependencies: true
2. Add @redocly/cli as a dependency to a workspace package
3. Run pnpm install with strict peer dependency checking enabled
4. See the error:

ERR_PNPM_PEER_DEP_ISSUES Unmet peer dependencies

└─┬ @redocly/cli 1.34.2
└─┬ @redocly/respect-core 1.34.2
└─┬ better-ajv-errors 1.2.0
└── ✕ missing peer ajv@"4.11.8 - 8"

Expected behavior

Installation should succeed with strict peer dependency checking enabled. @redocly/respect-core should add ajv as a dependency to ensure it's available for better-ajv-errors.

Logs

ERR_PNPM_PEER_DEP_ISSUES Unmet peer dependencies

└─┬ @redocly/cli 1.34.2
└─┬ @redocly/respect-core 1.34.2
└─┬ better-ajv-errors 1.2.0
└── ✕ missing peer ajv@"4.11.8 - 8"

Redocly version(s)*

@redocly/cli@1.34.2

Node.js version(s)

Node.js 22

OS, environment

Docker container and CI environments with strict peer dependency checking

Additional context

This issue occurs in environments where pnpm is configured with strictPeerDependencies: true (a best practice for dependency management). The missing peer dependency prevents automated builds and containerized deployments from succeeding.

[vadyvas]

@aklkv thanks for contributing! To help us reproduce it, could you please share a few extra details?

• pnpm version (pnpm -v)
• Have you tried @redocly/cli v2.x or newer? If yes, which exact version(s) and did the behavior change?
• Do you use any pnpm overrides? (e.g. pnpm.overrides)

Also, any additional reproduction context would be very helpful, for example:

• A minimal package.json + pnpm-workspace.yaml that reproduces it
• The output of pnpm why ajv in the failing setup

[aklkv]

sorry for delayed response, holidays happened 😆

pnpm -v: 10.20.0
I am now trying to upgrade to @redocly/cli v2 which results in the new but similar per deps issue:

this is dues to: strictPeerDependencies: true in our pnpm-workspace.yml

but I was able to sidestep the issue by:

peerDependencyRules:
  allowedVersions:
    core-js: '*'

so my original fix is no longer needed, I check if this changes have not introduced any side effect but generally wif package has peerDep it's a job of consumer to install it in this case is @redocly/cli but this is out very strict setup at fault. I will report back if this changes are fine. Thank you for your time

[alario-tang]

This issue also affects @redocly/openapi-core package.

ajv-formats@3.0.1 (dependency of @redocly/openapi-core) has peer dependency ajv@^8.0.0,
but since @redocly/openapi-core uses @redocly/ajv instead of standard ajv,
pnpm may resolve ajv@6 (from eslint) for ajv-formats, causing:

Cannot find module 'ajv/dist/compile/codegen'

The same fix in PR #2445 should be applied to @redocly/openapi-core:

"ajv": "npm:@redocly/ajv@8.17.1"

[vadyvas]

@aklkv @alario-tang @KevinNitroG
Changes are available starting from v2.14.5. Thank you 🙂