ajv: npm ERR! peer dep missing: ajv@^6.0.0, required by ajv-keywords@3.1.0
What version of Ajv are you using? Does the issue happen if you use the latest version?
Ajv options object
JSON Schema
Sample data
Your code
Validation result, data AFTER validation, error messages
What results did you expect?
Are you going to resolve the issue? a.txt
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 24 (7 by maintainers)
Commits related to this issue
- [npm] Adding ajv * Was raising npm ERR! peer dep missing without yarn * https://github.com/epoberezkin/ajv/issues/708 — committed to 3scale/porta by didierofrivia 6 years ago
- release: v2.0.0 * add ajv due to npm resolution issues https://github.com/ajv-validator/ajv/issues/708 — committed to kpsherva/react-invenio-forms by kpsherva a year ago
- release: v2.0.0 * add ajv due to npm resolution issues https://github.com/ajv-validator/ajv/issues/708 — committed to kpsherva/react-invenio-forms by kpsherva a year ago
- release: v2.0.0 * add ajv due to npm resolution issues https://github.com/ajv-validator/ajv/issues/708 — committed to kpsherva/react-invenio-forms by kpsherva a year ago
- release: v2.0.0 * add ajv due to npm resolution issues https://github.com/ajv-validator/ajv/issues/708 — committed to kpsherva/react-invenio-forms by kpsherva a year ago
- release: v2.0.0 * add ajv due to npm resolution issues https://github.com/ajv-validator/ajv/issues/708 — committed to kpsherva/react-invenio-forms by kpsherva a year ago
- release: v2.0.0 * add ajv due to npm resolution issues https://github.com/ajv-validator/ajv/issues/708 — committed to kpsherva/react-invenio-forms by kpsherva a year ago
- release: v2.0.0 * add ajv due to npm resolution issues https://github.com/ajv-validator/ajv/issues/708 — committed to inveniosoftware/react-invenio-forms by kpsherva a year ago
This is fixed by adding
ajv
in your project. The problem is almost certainly with npm itself.For reference, I think this might be an npm bug - seeing this problem with npm@5.3.0 and npm@3.10.10, but not with npm@5.6.0 or npm@2.15.11.
Found the npm issue: npm/npm#19877 (specifically this comment). Hope this helps!
@epoberezkin using yarn now and the specific issue above does not occur. thank you Eric