How's this compare to material-ui? I like material ui and it looks like you have some nice components, just curious what the x-factor is. Always up to use a new tool!
Show HN: Antd – A set of high-quality React components
31–40 of 107 posts
Re: Show HN: Antd – A set of high-quality React components
#32These components look and work great, but unfortunately are a real headache to retheme unless you want to pull in a sass/less toolchain in addition to what you'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. There is a standard for CSS variables and a very functional subset of their functionality can be compiled for older browsers at build…
I don't think your complaint is relevant here, especially since you provide no solution.
It bothers me that this reply is at the top of the comments.
Re: Show HN: Antd – A set of high-quality React components
#33It's so beautiful! Please please make something like this for react native too.
Re: Show HN: Antd – A set of high-quality React components
#34These components look and work great, but unfortunately are a real headache to retheme unless you want to pull in a sass/less toolchain in addition to what you'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. There is a standard for CSS variables and a very functional subset of their functionality can be compiled for older browsers at build…
SCSS (and to a lesser degree LESS) are basically industry standard now, if you are using react, you are almost certainly using one of the two preprocessors. I don't think your complaint is relevant here, especially since you provide no solution. It bothers me that this reply is at the top of the comments.
Re: Show HN: Antd – A set of high-quality React components
#35These components look and work great, but unfortunately are a real headache to retheme unless you want to pull in a sass/less toolchain in addition to what you'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. There is a standard for CSS variables and a very functional subset of their functionality can be compiled for older browsers at build…
SCSS (and to a lesser degree LESS) are basically industry standard now, if you are using react, you are almost certainly using one of the two preprocessors. I don't think your complaint is relevant here, especially since you provide no solution. It bothers me that this reply is at the top of the comments.
Re: Show HN: Antd – A set of high-quality React components
#36Earlier quoted context omitted.
SCSS (and to a lesser degree LESS) are basically industry standard now, if you are using react, you are almost certainly using one of the two preprocessors. I don't think your complaint is relevant here, especially since you provide no solution. It bothers me that this reply is at the top of the comments.
The argument about inline styles is valid, in my opinion. I've had to fork and keep updating from upstream several react components for the exact same reason.
Re: Show HN: Antd – A set of high-quality React components
#37These components look and work great, but unfortunately are a real headache to retheme unless you want to pull in a sass/less toolchain in addition to what you'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. There is a standard for CSS variables and a very functional subset of their functionality can be compiled for older browsers at build…
I'm one of the maintainers of ElementalUI, and Glen Maddern, the styled-components co-creator, one of the creators of CSS Modules. One of the biggest downsides of CSS Modules (and, by extension, every other styles in JavaScript library right now) is that theming is simply impossible. Building third-party component libraries is hard enough, but providing an easy-to-theme API wasn't a solved problem in the React world. Nobody has done it properly, and there is no agreed-upon way of doing this!
styled-components has built-in theming support[1] to solve this exact problem. (note: this is CSS-in-JS, not inline styles[2], so overriding is easy as pie too[3]) We're rebuilding ElementalUI with it right now and the next versions of react-toolbox and Belle will be built with it as well.
We also have ReactNative support, which nobody else has done before. Just because you're writing a universal React app with a third-party component library shouldn't mean switching between three or four different APIs to style your app. With styled-components, you can just use styled-components no matter what you're styling!
(If you're reading this, I'd love to have a chat with the Antd people about maybe moving to styled-components! You can reach me on Twitter at @mxstbr, just ping me there!)
[0]: https://styled-components.com
[1]: https://github.com/styled-components/styled-components#theming
[2]: mxstbr.blog/2016/11/inline-styles-vs-css-in-js
[3]: https://github.com/styled-components/styled-components#overriding-component-stylesRe: Show HN: Antd – A set of high-quality React components
#38What's the filesize for this?
The minified version is about 1MB, see https://unpkg.com/antd@2.5.0/dist/ . But you can import component individually by using this babel plugin https://github.com/ant-design/babel-plugin-import , see https://ant.design/docs/react/getting-started#Import-on-Dema...
Re: Show HN: Antd – A set of high-quality React components
#39Is this by Stripe? The components look just like their dashboard.