NPM ERROR

[hui55]

npm WARN ajv-keywords@3.1.0 requires a peer of ajv@^6.0.0 but none is installed. You must install peer dependencies yourself.

npm ERR! peer dep missing: ajv@^6.0.0, required by ajv-keywords@3.1.0

[hui55]

When I execute npm list -g --depth=0 this error is listed twice:

npm ERR! peer dep missing: ajv@^6.0.0, required by ajv-keywords@3.1.0

[bboydflo]

I got the same error, using a mac

[bboydflo]

I have tried the same in windows and it works without any problems.

[developit]

See this issue:
ajv-validator/ajv-keywords#56

[bboydflo]

somebody pointed that that might be an npm issue. try to update sudo npm install -g npm might help.

[reznord]

It is generally not recommend to use npm with sudo

[lucaseverett]

Just a note for anyone else having this problem: Using "yarn global add preact-cli" installs without this error.

[Luxcium]

Is this issue include the circular problem I have in (ajv-validator/ajv-keywords#74) and repeated in (ajv-validator/ajv-keywords#56) about:

installing ajv@^6.0.0 gives this error -> ajv-keywords@2.1.1 requires a peer of ajv@^5.0.0

and

installing ajv@^5.0.0 gives this error -> ajv-keywords@3.2.0 requires a peer of ajv@^6.0.0

using a mac with npm -v = 6.4.1

@babel/cli = v. 7.1.2
@babel/core = v. 7.1.0
webpack = v. 4.19.1
typescript-eslint-parser = v. 20.1.1

[pldg]

I've the same problem.

npm install -g preact-cli prompt some warnings:

npm WARN ajv-keywords@3.4.1 requires a peer of ajv@^6.9.1 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/preact-cli/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

If I run npm list -g --depth=0 print two errors:

npm ERR! peer dep missing: ajv@^6.9.1, required by ajv-keywords@3.4.1
npm ERR! peer dep missing: ajv@^6.9.1, required by ajv-keywords@3.4.1

Any solution (without using yarn)?

[ForsakenHarmony]

ajv-validator/ajv#708 (comment)

Still an npm issue?