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.
dependency cls-hooked won't resolve
See original GitHub issuehi. since me updating npm to version 7 i am facing serious issues with your dependency of cls-hooked.
in my local dev environment everything is fine but in CI this dependency won’t be resolved since npm cannot access it without an ssh key. this is because npm resolves the dependency as git+ssh://git@github... since the update.
so my question is: what is the reason for using the unreleased version 4.3.0 of cls-hooked and not just depending on the npm released 4.2.2?
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Don’t worry. If I couldn’t had fixed it I would’ve been more annoying 😉
I patched it by resolving it explicitly and adding it as my dependency in package.json so I could define what protocol to use. So it doesn’t bother me at the moment but it is an unused dependency 😉