Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
2.0.2 npm ERR! cb() never called!
See original GitHub issueon yarn install
error An unexpected error occurred: "https://registry.yarnpkg.com/eslint-plugin-html/-/eslint-plugin-html-2.0.2.tgz: invalid tar file".
on npm install eslint-plugin-html@2.0.2
npm ERR! cb() never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! <https://github.com/npm/npm/issues>
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:10 (4 by maintainers)
Top Results From Across the Web
npm ERR cb() never called - node.js - Stack Overflow
If you have npm version 5 or above, try this first: $ sudo npm cache verify. Otherwise: $ sudo npm cache clean. My...
Read more >How to solve npm ERR! cb() never called - Midi - Medium
How to solve npm ERR! cb() never called · Delete your 'package-lock.json' file. · Run the following command from the root folder of...
Read more >npm install: "cb() never called" · Issue #17839 - GitHub
I'm opening this issue because: npm is crashing. npm is producing an incorrect install. npm is doing something I don't understand.
Read more >How to fix npm err! cb() never called! issue - Nathan Sebhastian
How to fix npm err! cb() never called! issue · Check the npm version and cache · Delete the package-lock.json file · Check...
Read more >How to fix "npm ERR cb() never called" - ReleaseCandidate.dev
If this issue comes up on your local development machine, it might pay to clear the cache: npm cache clean -force · Secondly,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I just republished my package, it should work now.
Same issue here. Worked around it by installing previous version
npm install eslint-plugin-html@2.0.1