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.
`@hapi/joi` dependency - necessary?
See original GitHub issueJust evaluating this lib for use in a project and the one issue that stood out for me was the dependency on @hapi/joi, which has a chain of various dependencies.
This is only used in src for validateEvent. This isn’t exported or part of the package’s public API, but it’s used as part of createEvent. Is it really necessary to validate the package’s output at runtime? Seems like more of a job for unit tests.
If it’s possible to move @hapi/joi into devDependencies and drop this runtime check that’d be a nice win (and presumably also a good performance boost for createEvent, if that matters)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:9 (5 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
Great suggestion, I’ll take a look
Heard and merged!