Stuck on an issue?
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.
Moving away from SCSS
See original GitHub issueAre there any plans to move away from SCSS to avoid the @import ... styles step? Having SCSS as a dependency only to use the charting library is not ideal for projects which don’t use SCSS.
Inline styles or styled-components would be a good alternative.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Styled Components in React: Moving away from SCSS - FloQast
Learn how Styled Components can help you better manage the CSS that style your React Components and decouple your monolithic stylesheets.
Read more >Stepping away from Sass - Cathy Dutton
My latest site redesign and why I left out Sass and media queries in favour of native CSS grid, calc, viewport units and...
Read more >Moving from SASS to PostCSS, why what and how
Gracefully moving from SCSS to PostCSS To stay on topic I'll do the switch based on SCSS writing style, so I'll need $variables,...
Read more >Best practices for moving css styles into Sass files
1. Hi bob, best practices questions are off-topic at Stack Overflow because they are opinion-based (even if most people share the same opinion)....
Read more >Why We're Breaking Up with CSS-in-JS - DEV Community
To understand why our team is moving away from the technology, we need to explore the real-world performance impact of CSS-in-JS.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’ve talked about this before, and maybe now is the time to completely switch over to inline styles as we’ve been in a mixed context (of some inline/some stylesheet) for a while. I think in order to complete this task the styling system would need to be added to the legends, refined in the treemap and radial chart.
All that is to say, i think this should be totally possible. I would push against use styled-components as we already have quite a bit of investment in inline styling, but I would hear other opinions. If we were to carry this out, this would be a major-ish level breaking change, so it’s worth considering deeply.
Inline styles library are legions, what about people who are already constrained by one?
For reference, Material-ui makes a good case for styling solution interop https://material-ui-1dab0.firebaseapp.com/guides/interoperability/