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

Error when running npm install with 1.2.2 #15

Closed
mh1622 opened this issue May 17, 2021 · 14 comments
Closed

Error when running npm install with 1.2.2 #15

mh1622 opened this issue May 17, 2021 · 14 comments

Comments

@mh1622
Copy link

mh1622 commented May 17, 2021

Describe the bug

npm ERR! code ENOENT
npm ERR! syscall chmod
npm ERR! path /home/USER/PROJECT/node_modules/istanbul-badges-readme/lib/index.js
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, chmod '/home/USER/PROJECT/node_modules/istanbul-badges-readme/lib/index.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

To Reproduce

  1. Change dependency version from 1.2.1 to 1.2.2
  2. Run npm install

Additional context
1.2.1 works fine locally and in github actions. 1.2.2 fails in both environments.
Node v14.16.0
Npm 6.14.11

@olavoparno
Copy link
Member

Hello @mh1622 thanks for the report. I will look into it as soon as possible, for now please do use the previous version :)

@venturalp
Copy link
Collaborator

I've made a pull request in an attempt to fix this bug #16

@venturalp
Copy link
Collaborator

@all-contributors please add @mh1622 for bug

@allcontributors
Copy link
Contributor

@venturalp

This project's configuration file has malformed JSON: .all-contributorsrc. Error:: Unexpected token ] in JSON at position 2086

@olavoparno
Copy link
Member

@all-contributors please add @mh1622 for bug

@allcontributors
Copy link
Contributor

@olavoparno

I've put up a pull request to add @mh1622! 🎉

@venturalp venturalp reopened this May 17, 2021
@venturalp
Copy link
Collaborator

@mh1622 problem solved, thanks for letting us know

@olavoparno
Copy link
Member

@mh1622 thank you again for the issue. Could you please check version 1.3.0 and give us a feedback wether the problem is solved or not?

@mh1622
Copy link
Author

mh1622 commented May 18, 2021

This appears fixed now. Impressive turnaround time! 👏

@OlehDutchenko
Copy link

OlehDutchenko commented May 21, 2021

Faced with this error today
trying 1.2.2+ version (((

  • macOS Big Sur
  • node 16.0.0
  • npm 7.10.0

1.2.0 version works fine

@olavoparno
Copy link
Member

Faced with this error today
trying 1.2.2+ version (((

  • macOS Big Sur
  • node 16.0.0
  • npm 7.10.0

1.2.0 version works fine

Hello, @dutchenkoOleg , thanks for the issue. Reopening for further investigation.

@olavoparno olavoparno reopened this May 21, 2021
This was referenced May 21, 2021
@olavoparno
Copy link
Member

We are deeply sorry the inconvenience and after a thorough troubleshooting we have finally come to a solution.

Please do check it with version 1.3.4 and if the problem is either solved or remaining, be so kind and reply us.

Thank you for using the library.

@all-contributors please add @dutchenkoOleg for bug

@allcontributors
Copy link
Contributor

@olavoparno

I've put up a pull request to add @dutchenkoOleg! 🎉

@OlehDutchenko
Copy link

Sorry for my late. I tested - it works fine! Thanks!

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

No branches or pull requests

4 participants