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

[developer-73]

I am facing this build error in "ajv-keywords" after installing packages with npm install --legacy-peer-deps
Error: Cannot find module 'ajv/dist/compile/codegen'

Background:

Consider the following dependency trees:

|__@eslint
|[email protected]          <<<<<---- |
|[email protected]       >>---^  Incompatible with [email protected]
|[email protected]
         |[email protected]

|__@eslint
      |[email protected]
|[email protected]            <<<<<---- |
|[email protected]         >>---^  Compatible with [email protected]
|[email protected]

Notice: with npm install --legacy-peer-deps (1st tree) gives incorrect tree structure and not with npm install (2nd one).

npm install --legacy-peer-deps results in following error on npm run build:

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

I have prepared a repo at https://github.com/developer-73/ajv-peerdep-issue.
I am using following devDependencies ::

"babel-loader": "9.1.2",
"eslint": "8.36.0"

• [email protected] depends on avj@^6.12.4
• babel-loader@^9.1.2 depends on schema-utils@^4.0.0 which further depends on :
  ajv@^8.8.0 and ajv-keywords@^5.0.0, where ajv-keywords has a peer dependency on ajv@^8.8.0

Run npm install --legacy-peer-deps and notice the incorrect tree structure in node_modules i.e. [email protected]
gets hoisted on the root level of node_modules and is using incorrect version of [email protected].
This is a problem because the hoisted ajv-keywords@^5.0.0 will not have its peer dependency on ajv@^8.8.0 met.

Note: This works correctly on npm < 7

Possible solution: Can you please add "ajv" as your packages dependencies instead of devDependency? This will ensure "ajv-keywords" to get latest "ajv" version

**Environment**
npm: 8.19.4
Node.js: 18.15.0
OS Name: Mac OS

[parker-siroishka]

I seem to be encountering the very same issue you have. Were you able to find a fix for it?

[s100]

In order to prevent this disagreement at the top level of node_modules, I have found that a workaround is to manually add dependencies on specific, agreeing versions of schema-utils, ajv and ajv-keywords.

So in your package.json under "dependencies" or "devDependencies", try adding either:

"schema-utils": "^3.3.0",
"ajv": "^6.12.6",
"ajv-keywords": "^3.5.2",

or:

"schema-utils": "^4.2.0",
"ajv": "^8.12.0",
"ajv-keywords": "^5.1.0",