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.
Incorrect TypeScript errors about a missing css prop
See original GitHub issueCurrent Behavior:
The error we’re seeing is this:
This may be a duplicate of https://github.com/emotion-js/emotion/issues/693 but I’m not yet convinced because we’re on newer versions of all of these:
and we still see this odd error in TypeScript.
I’m not entirely sure why.
To Reproduce Click View Code here
The component’s source code is: https://github.com/contiamo/operational-ui/blob/7f3a10e1e24ff04b90a54940644d3c9340ebaa1c/src/Typography/FinePrint/index.tsx#L3-L13
Expected behavior: Clean compilation.
Environment information:
Issue Analytics
- State:
- Created 4 years ago
- Reactions:13
- Comments:7 (4 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 ran into the same issue today while I was working on a package where I was importing components from another package that were created (and typed) as
styled()components from@emotion/styled, all on version10.0.17.The issue went away after adding a
import '@emotion/core'to theindex.tsfile of my package. I think the problem resided in the fact that the type definitions to support thecssprop would otherwise not be properly resolved by TypeScript somehow.Typings are currently getting a serious makeover in https://github.com/emotion-js/emotion/pull/1501 and we plan to rethink how the theme can be typed. Closing this to clear up the issue tracker, but if you are interested in this please follow that PR, give your feedback if necessary and stay tuned for upcoming changes!