Closed zeke closed 4 years ago
False alarm. It was my environment. npm cache clean --force
did the trick. Closing.
Yeah, sorry, didn't look into your issue earlier, as it had no repro and npm wouldn't even allow publishing a package with broken package.json, so assumed it was on your end until proven otherwise :)
On Tue, Mar 3, 2020 at 4:36 PM Zeke Sikelianos notifications@github.com wrote:
Closed #546 https://github.com/immerjs/immer/issues/546.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/immerjs/immer/issues/546?email_source=notifications&email_token=AAN4NBAIUERTMOEC5UIBN6DRFUWXJA5CNFSM4K7B2UDKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOXBNIMEQ#event-3092940306, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN4NBBUZQXGAMDEU4NE46DRFUWXJANCNFSM4K7B2UDA .
npm cache clean --force et après tu fais npm install -g npm à la fin de l'installation tu executes ta commande npm install immer
I had the same issue.. npm cach clean --force wasn't working for me. So i deleted node modules folder ran npm i once again.. and boom, it worked!
For anyone else having the same issues. :)
🐛 Bug Report
Hello, @mweststrate and maintainers 👋
I'm unable to install this package, but am not having trouble installing other packages.
Repro
To Reproduce
Environment
latest