Show HN: Antd – A set of high-quality React components
These components look and work great, but unfortunately are a real headache to retheme unless you want to pull in a sass&#x2F;less toolchain in addition to what you&#x27;re currently using. This is a pain in the ass if you already have your theme variables set up in one compiles-to-CSS language.<p>There is a standard for CSS variables and a very functional subset of their functionality can be compiled for older browsers at build time: <a href="http:&#x2F;&#x2F;cssnext.io" rel="nofollow">http:&#x2F;&#x2F;cssnext.io</a>, yet as far as I can tell, all of these component frameworks impose some other nonstandard compiles-to-CSS language or one of many possible APIs for writing inline styles.<p>Inline styles seem to be a trend at the moment but I can only assume the people driving this movement haven&#x27;t had the experience of working with 3rd party components (which you may or may not have the source for) and needing to alter something the designers didn&#x27;t expose and simply having no simple options because the damn inline style can&#x27;t be overridden even by !important. Now you&#x27;ve got to fork whole the f&#x27;ing component, possibly multiple, each of which potentially coming with yet another different compiles-to-CSS toolchain all because you wanted to add a single line of CSS.<p>Admittedly, antd doesn&#x27;t use inline styles si the above doesn&#x27;t apply here, but having to maintain a custom builder for antd in order to change some fonts and a few colors was a frustrating experience. Not sure what a good solution is until CSS variables get more browser adoption, but it&#x27;d be great if we could collectively start standardizing on standards.