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.
forwardRefWithAs in Typescript 4.2
See original GitHub issue🐛 Bug report
Keeping this brief and more as a heads up rather than a report since 4.2 just released 2 days ago. My team tried to upgrade and our components that used forwardRefWithAs broke.
Note: we aren’t using reach-ui, just your forwardRefWithAs hack
Current Behavior
After upgrading to Typescript 4.2 forwardRefWithAs has stopped working and components using as get this tsc error Expression produces a union type that is too complex to represent.
If we set as={asProp as 'div'} on the component then the error goes away, so I think the default type of React.ElementType<any> is now causing issues.
Expected behavior
forwardRefWithAs is usable with future versions of Typescript
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (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
Yeah, it was a shockingly easy conversion. We converted about 16 components of varying complexity from forward ref with as in less than a day
This should hopefully be addressed in the next release. I’ve removed the utility and simplified typing a bit. See notes in https://github.com/reach/reach-ui/commit/fb6ad2077c8b9d5fd6c476ad2efbec60f518443f