Open yalishanda42 opened 4 years ago
I got the same issue, what worked for me was going to the directory where the package is deleted node_modules and run npm i
inside the directory for the package again.
Once you have done this run npm audit fix
. Then try to rebuild the package and it should all work!
I got the same issue, what worked for me was going to the directory where the package is deleted node_modules and run npm I inside the directory for the package again.
If you need more info just let me know and I can give you a detailed list of what I did.
I got the same issue, what worked for me was going to the directory where the package is deleted node_modules and run
npm i
inside the directory for the package again. Once you have done this runnpm audit fix
I got this same issue. I tried your fix but I'm still getting the error.
I got the same issue, what worked for me was going to the directory where the package is deleted node_modules and run
npm i
inside the directory for the package again. Once you have done this runnpm audit fix
I got this same issue. I tried your fix but I'm still getting the error.
Did you try rebuilding the package once you did all of this?
I got the same issue, what worked for me was going to the directory where the package is deleted node_modules and run
npm i
inside the directory for the package again. Once you have done this runnpm audit fix
I got this same issue. I tried your fix but I'm still getting the error.
Did you try rebuilding the package once you did all of this?
I did now, and it works. Thanks.
@allexks Just wondering in order for this issue to be marked as closed, has the issue been fixed?
@allexks Just wondering in order for this issue to be marked as closed, has the issue been fixed?
I perfomed the workaround that you suggested and it fixed the problem. Does this count?
Step to reproduce
Stacktrace
Information
Platform: macOS 10.15.4
Atom: 1.47.0
Package Version: 2.0.2
Didn't happen until 2 or 3 days ago. Haven't installed other Atom packages in a while.