Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firebase functions deploy npm error #58

Closed
shashank-shinde opened this issue Feb 28, 2018 · 4 comments
Closed

Firebase functions deploy npm error #58

shashank-shinde opened this issue Feb 28, 2018 · 4 comments

Comments

@shashank-shinde
Copy link

npm WARN ajv-keywords@3.1.0 requires a peer 0f ajv@A6.0.0 but none is installed. You must install peer dependencies yourself.

For screenshot please refer- Firebase functions deploy npm error

@epoberezkin
Copy link
Member

same as #56 ?

@shashank-shinde
Copy link
Author

How to fix it?

@shashank-shinde
Copy link
Author

Here is detailed log:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli '--prefix',
1 verbose cli '$RESOURCE_DIR',
1 verbose cli 'run',
1 verbose cli 'lint' ]
2 info using npm@5.6.0
3 info using node@v9.6.1
4 verbose stack Error: ENOENT: no such file or directory, open 'E:\Android_Projects\Booking$RESOURCE_DIR\package.json'
5 verbose cwd E:\Android_Projects\Booking
6 verbose Windows_NT 6.1.7601
7 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "--prefix" "$RESOURCE_DIR" "run" "lint"
8 verbose node v9.6.1
9 verbose npm v5.6.0
10 error path E:\Android_Projects\Booking$RESOURCE_DIR\package.json
11 error code ENOENT
12 error errno -4058
13 error syscall open
14 error enoent ENOENT: no such file or directory, open 'E:\Android_Projects\Booking$RESOURCE_DIR\package.json'
15 error enoent This is related to npm not being able to find a file.
16 verbose exit [ -4058, true ]

@epoberezkin
Copy link
Member

I don’t see how it can be ajv issue. See ajv-validator/ajv#708
The issue must be either with the tools you use or with npm.

Closing it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants