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.
Web Components support
See original GitHub issueFrom a cursory glance at web components, supporting them should be possible. This should probably live at another entry point (like import styled from 'styled-components/web'), and the only thing that would need to happen is instead of returning a react component, we return a web component.
The entire react-specific part of styled-components lives in a single, tiny file: src/models/StyledComponent.js. (and StyledNativeComponent.js)
I won’t be able to really dig into this until after #120 and #59, so if somebody wants to pick this up it’d be greatly appreciated!
Issue Analytics
- State:
- Created 7 years ago
- Reactions:8
- Comments:19 (12 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
@yuki24 “Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress”
This sounds like more than just a React project! The concept of styled-components could fairly easily be applied to web components, as I’ve demonstrated here.
I am still very interested in the original concept brought up by @mxstbr in using a
styled-components/webentrypoint for web component support.@mxstbr more interest for it now!