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.
Why `cls-hooked` is peer dependency?
See original GitHub issueIMHO peer dependencies are required if you are building plugins for some library. For example lets say you are building webpack plugin then webpack will become your peer dependency.
And some who is using webpack can use use your plugin.
But here I think we only need to use this library cls-rtracer, and I am not using cls-hooked.
By this logic I think we can add cls-hooked under your dependencies section from peerDependencies.
Any thoughts?
I can raise a pull request if you guys agree.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5 (3 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
Thanks @puzpuzpuz for the explanation. Waiting for them to get merged.
Guys, it seems like there should be only one cls-hooked instance present. Take a look at this line. With multiple instances of cls-hooked there will be conflicts.