antd@3.0

A place to discuss what we want/have to do in antd@3.0:

React@16 relative

• React Umbrella support #5377
• Refactor all the ref: string to ref: function

…

antd’s own

• provide es2015 module format like this
• Remove all deparated features
  1. and theirs warning
  2. and then add new warning of upgrade tips
• New Components
  • List https://github.com/ant-design/ant-design/issues/4905
  • Divider https://github.com/ant-design/ant-design/issues/6812
• Default language of LocaleProvider should be changed to en
• Less aggressive global style: https://github.com/ant-design/ant-design/issues/4331
• Better default typography: https://github.com/ant-design/ant-design/issues/6162
• ~~Component should work with HOC: https://github.com/ant-design/ant-design/issues/4853~~
• WeekPicker https://github.com/ant-design/ant-design/issues/3825
• Rewrite Steps https://github.com/react-component/steps/pull/39
• Contextmenu dropdown https://github.com/ant-design/ant-design/issues/7232
• external moment while building dist file

  // We need to link moment before antd's dist file after antd@3.0
  <script src="moment.js"></script>
  <script src="antd.js"></script>
  

• Refactor Menu for delay and auto overflow: https://github.com/ant-design/ant-design/issues/2830
• Mention placement: https://github.com/ant-design/ant-design/issues/6663
• TypeScript document: https://github.com/ant-design/ant-design/pull/6193
• Preact support https://github.com/ant-design/ant-design/issues/5048 …

Tools

• Tools for upgrading antd from 2 to 3 https://github.com/ant-design/ant-design/issues/3759#issuecomment-272353773
• Webpack@2 support cc @sorrycc
  • Roadhog
  • atool-build
  • dva-cli

…

Ant Design Specification relative

• Bigger default font size, following our designer’s plan.

…

Site ant.design

• Rewrite demo in TypeScript #5390
• Let demo code editable or a Playground #5140

…

[kitten]

@paranoidjk @afc163 @benjycui

Hiya, I’m one of the styled-components core-contributors and found this thread due to an opened issue on our repo (see above), that informed me that this lib doesn’t support SC. By chance I then found this conversation 😉 – Ok, context aside now

the autoprefixer library may not very reliable compare to postcss

We’ve carefully chosen stylis and are closely working together with @thysultan, who develops it. We wouldn’t have chosen it, if it wasn’t a worthy replacement of PostCSS and the few issues that it had (a couple of missing prefixes in v3), were resolved very quickly. The v2 itself has been in the making for a few months btw, and is now finally out. We can definitely vouch on that part. Let this implementation detail be our worry, if you’d go with SC 😄

The file you’re pointing to is not in use and was deleted now btw, and is part of the old auto-prefixing with inline-style-prefixer. But even that is (and was for us) a very, very, very trusted solution through out the css-in-js community by @rofrischmann.

Or we can say, once pick css-in-js, we will lose convenience of post-css plugin system, such as px-to-rem?

Since in interpolations in our tagged template literals you can just use any JS, simple functions can replace all that stuff. We actually have a separate project called “polished” that is like the lodash for CSS-in-JS and comes with all mixins (i.e. helper functions) that you’d expect from SASS/LESS and the likes: https://polished.js.org

(We indeed neither use PostCSS anymore as mentioned above, nor have we supported its plugins btw)

we have to remain whole current css classname for compatibility, while styled-components will generated it’s own classname for style, it will be redundancy and hard to maintain?

If you need to attach custom classnames, you can easily use our .attrs method, which allows you to attach additional props to a component. For example:

const ButtonLink = styled.a.attrs({
  className: 'your-custom-extra-classname'
})`
   ... // css and stuff
`

Some more goodies and features:

• You write just CSS (as you might already know), and the only additions are ampersands and nestedness
• There’s no styles+component mapping
• Everything’s a component
• You can write mixins/shared styles with our css helper

I’m here if you need more help. If you need some more info though, check out our new website 💯 https://styled-components.com

[Enalmada]

+1 for styled-components/emotion/fela support in a future release.