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.
question: why "types/react" is included in deps?
See original GitHub issueI’m not an experienced Typescript, but I dont think it is a best practice to directly depend on @types/react. Correct me if im wrong here and if it should be there please explain why.
Another aspect of this direct dependency is that there are 4 types of react consumers: raw js, compile2js lang, flowtype and typescript consumers. Even If it makes sense for typescript users that react-css directly depends on “types/react”, it introduces download, bandwidth and build time tax for everybody. I dont think it is fair
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:15 (15 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
I think the best option is to have in optional dependencies and in dev deps.
True, and flow types are the complete source code 🤣