Replies: 38 comments 45 replies
-
|
We should first create a next branch |
Beta Was this translation helpful? Give feedback.
-
|
Compatibility with React 19 and Next.js 15. |
Beta Was this translation helpful? Give feedback.
-
|
i think better React version adjust to >= 19 so that can use new react hooks inside antd component make it more easily |
Beta Was this translation helpful? Give feedback.
-
|
19 added hooks may more improve the web app development experience. But for component side, I guess 18 hooks is much more important (just for personal opinion ) |
Beta Was this translation helpful? Give feedback.
-
People who upgrade to antd v6 will definitely upgrade to react 19. I think it is enough to just be compatible with react 19. |
Beta Was this translation helpful? Give feedback.
-
Upgrade to antd v6 is much easier than React 19. Since ref will be the props which mean web app upgrade need modify to handle this case: const myRef = React.useRef();
const mergedRef = mergeRef(ref, myRef);
<MyComponent
ref={mergedRef}
{...props}
/> |
Beta Was this translation helpful? Give feedback.
-
|
Today, Antd 3 still has a huge user base. Even if we make compatibility as extreme as possible, there are still many people who are unwilling to change major versions. Since this is an opportunity to cut off from the past, it is better to cut off more thoroughly, so I suggest supporting only react 19. |
Beta Was this translation helpful? Give feedback.
-
|
very nice, support only react 19 |
Beta Was this translation helpful? Give feedback.
-
|
i really want to upgrade to Next.js 15 so i can use the new Turbopack. Webpack is so slow |
Beta Was this translation helpful? Give feedback.
-
|
Just in case you don't know, this combination actually works: nextjs 15, pages router (this is important), react 18.x, antd 5. We don't really need rsc or other app Router niceties for our use case but turbopack works great. App Router in next 15 can only be used with react 19.x |
Beta Was this translation helpful? Give feedback.
-
|
+1, I have tried with next 15 + turbo , it can speed my dev mode with 40% time reduced. But core issue is antd not compatible with react19 |
Beta Was this translation helpful? Give feedback.
-
|
when this project start? |
Beta Was this translation helpful? Give feedback.
-
suggest to deprecated all the other className like |
Beta Was this translation helpful? Give feedback.
-
|
Sounds good, but I think it would be good to separate from |
Beta Was this translation helpful? Give feedback.
-
|
Agree to remove |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
No, I mean that OP's suggestion should not merge with the native |
Beta Was this translation helpful? Give feedback.
-
|
guys, don't forget about accessibility! |
Beta Was this translation helpful? Give feedback.
-
|
I think a11y can be continue improve. Not start in v6, but now : ) |
Beta Was this translation helpful? Give feedback.
-
|
I think a good feature is to pre-compile with
|
Beta Was this translation helpful? Give feedback.
-
|
强烈建议从 react 19 开始支持。 我使用 react 19 已经半年多了，我的感受是 React 19 是一个全新的、面向未来的版本。因此 antd 的新版本应该至少是基于 react 19 来开发，而不仅仅是兼容 react 19。 如果还继续兼容 react 18 的话，那么也就意味着许多新的 hook 和特性可能不会被使用，依然是基于老版本 react 18 来开发。 可能会出现的隐患有
如果完全基于 react 19 的话，开发者可以得到一个更加纯粹的版本。万分期待 ing |
Beta Was this translation helpful? Give feedback.
-
|
@arvinxx 有一个问题，就是如果 antd 新增了能力，你们是否会放弃在 v5.x 的版本中新增？仅支持 v6.x |
Beta Was this translation helpful? Give feedback.
-
按以往的惯例，新功能是只会做在新的大版本。旧版本承诺 bugfix 一年，但不会把新功能再补到旧大版本里。所以业务如果要享用到新特性，例如语义化 DOM 等，必须要升级到 v6。 |
Beta Was this translation helpful? Give feedback.
-
正如上面所说，为了业务的持续健康迭代，只有到了新版本才能持续享受到不断新增的功能。业务提的新需求也只会在新版本里做，那业务必须要升级到 antd v6，但此时业务不一定会有动力升级 react19 。为了说要用某个新功能必须升级 react19 ，这个逻辑业务是不会买单的。
据我所知，蚂蚁内应该能有。除非明确不迭代和不维护的业务应用，剩下的大部分应用都会在 2 年内升级到新版本（业务主动升级 或 组织架构 push 升级），这也是为什么 antd 能这样持续维护的核心原因。所以平滑升级一直是 antd 升级大版本的一个很重要的考量因素，而不是一味追最新的技术栈，不管老用户死活。 |
Beta Was this translation helpful? Give feedback.
-
如果是这样的话你们的想法我能 get。老版本不会增加新的功能，所以你们会觉得如果增加了新的功能，老用户会想要为了使用新能力而升级。但不是为了 react 19 而升级。 |
Beta Was this translation helpful? Give feedback.
-
关于新增 feature一般启动大版本时，旧的版本就会进入维护状态，不再新增 feature。大版本一般都会对底层做一部分重构，如果都支持则会遇到这个版本做了，但是代码在下个版本其实是不用的情况。又比如你所提到的，React 新版本的 hooks 在旧版本没有。在提升版本的时候，就可以用新的 hooks 了。 关于兼容性评估下来，18 是业务应用与业界技术的交集。理由如 @arvinxx 提到的，过于激进的版本会让没有精力维护的业务技术栈被锁死在特定版本。而 React 18 是一个业务升级几乎不会有修改成本的版本（API 改动在框架层处理掉，UI 部分则是无感的），那提升 antd 也就可以顺带上来了。如果是到 19，是会有大量回归问题。 |
Beta Was this translation helpful? Give feedback.
-
|
I heard someone say that React 19 dares to release breaking changes, why should Ant Design v6 care about older users?(React 18) |
Beta Was this translation helpful? Give feedback.
-
|
强烈建议从 react 19 开始支持。 |
Beta Was this translation helpful? Give feedback.
-
|
Is there an ETA for when this will be available? |
Beta Was this translation helpful? Give feedback.
-
|
I'm just here to see when to support react19. |
Beta Was this translation helpful? Give feedback.
-
|
Looks like there is a plan 😌 |
Beta Was this translation helpful? Give feedback.
-
|
antd最新版本不支持react@19,antd5确实会报错，用不了 |
Beta Was this translation helpful? Give feedback.
-
支持19也不是一两天的事，没个一两个月也搞不定的 |
Beta Was this translation helpful? Give feedback.
-
我也是类似的情况，不过我是要在已经开发了的一年的项目上做升级，但是又特别依赖 antd，导致 antd 不支持我整个项目都不好升级。改成别的组件直接会带来不少的开发工作量。真希望能尽早relase antd 6.x |
Beta Was this translation helpful? Give feedback.
-
|
我的建议是先用 React 18 + antd 5，然后可以把 |
Beta Was this translation helpful? Give feedback.
-
|
除了这两个错误之外，还有遇到其他错误吗？ |
Beta Was this translation helpful? Give feedback.
-
其实你用 React 19， 95% 的写法是和 18一样的，只是 React19 开始不需要写 forwardRef，以及未来等 Compiler 成熟之后不需要再包 memo 了。如果你的应用场景对 ref 的依赖度不高（正常情况的业务也不太需要ref），先用 18 没啥问题的。 至于 React19 里一些对 Context 使用的改造（比如直接就可以 |
Beta Was this translation helpful? Give feedback.
-
|
如果不做 RSC 相关的开发，React 19 并没有什么特别大的不同，v6 从 React 18 开始支持，兼容 React 19 这样就很好。 |
Beta Was this translation helpful? Give feedback.
-
|
能否 先 发布一个 预发布版本 来支持 React 19，React 19已经发布一周了，是时候规划了。 |
Beta Was this translation helpful? Give feedback.
-
|
关于是否兼容 React 18 的争论，我认为还是应该兼容的，不过你们可以收集一下 antd4 -> antd5 的项目，看看有多少是和 React 一起升级的，至少我们公司是先处理的 React 大版本升级，UI 框架的升级多少会在视觉上发生改变，所以对于我们来说优先级反而更低。另外，希望加快 antd5 对 React 19 的适配！ |
Beta Was this translation helpful? Give feedback.
-
|
有动力升级antd6，早把react升级到19了。 |
Beta Was this translation helpful? Give feedback.
-
如果一个项目决定升级 react19 和 antd6，可能是分两个阶段，先升级 antd6，线上验证一段时间，再升级 react19，这两个阶段中间是可以正常做业务需求的。如果 antd6 只支持 react 19，那就必须两个一起升级，对于一些大型项目来说，周期会有很长，期间很多业务需求也不能停，不断合并分支解决冲突是非常耗时费力的。 |
Beta Was this translation helpful? Give feedback.
-
你弄错了先后(没有先发布的A包兼容后发布的B包的逻辑)，因为react19是先发布的，所以项目一定是先升级react19，再升级antd6。 |
Beta Was this translation helpful? Give feedback.
-
|
@zhi-he antd 5.x 已经支持 React 19 了。https://ant.design/docs/react/v5-for-19-cn |
Beta Was this translation helpful? Give feedback.
-
|
@afc163 感谢，我会尝试着升级。 |
Beta Was this translation helpful? Give feedback.
-
|
as someone who has to read ant design source, i wish antd6 take the path of minimizing outside dependencies and merge all packages especially rc-* repos into the main repo under components this should open up the road to reducing the bundle size, code complexity size and unnecessary nesting as well less dependencies - less pressure on vulnerabilities scanning too https://github.com/ant-design/ant-design/tree/master/components same with hooks to unify experience and reuse i would also have closer look at upcoming projects from Upcoming features can significantly improve dev experience and overall experience of people like myself wishing to experiment with source code Transformer The biggest objection I hear about ant - too many dependencies to grasp and study p.s. my chance to say thank you to all maintainers - guys, you created the best react kit for multilingual interfaces! respect to your work and endless efforts |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
希望能够移除 |
Beta Was this translation helpful? Give feedback.
-
|
这样的话所有的子组件都要单独导出一遍，感觉要改的地方有点多，另外还要考虑子组件作为单独组件的话，是否需要重新命名 |
Beta Was this translation helpful? Give feedback.
-
可以提供一个胶水包，旧项目可以引入这个包，把原有子组件再链接回去。 // app
import { Input } 'antd-legacy';
<Input.OTA/>// antd-legacy
import { Input, OTAInput } from 'antd';
Input.OTA = OTAInput;
export { Input }; |
Beta Was this translation helpful? Give feedback.
-
|
同意。此外这种写法也 RSC 不友好 |
Beta Was this translation helpful? Give feedback.
-
|
叫InputOAT吧，搜索好搜 |
Beta Was this translation helpful? Give feedback.
-
|
+1，很好 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
建议在这个版本解决 Menu 组件长期以来的性能问题：#32681 ， #41249 似乎由于历史包袱，官方不敢大刀阔斧去改 |
Beta Was this translation helpful? Give feedback.
-
|
+1 , menu性能真的很差… |
Beta Was this translation helpful? Give feedback.
-
|
Tooltip、Popconfirm、Popover 能否考虑合并为 Popover？Tooltip 实际上只是颜色样式略微不同，Popover 实际上只是提供了图标和两个操作按钮，功能都太少，作为单独的组件有点浪费。 |
Beta Was this translation helpful? Give feedback.
-
|
React 应用通常都将自己的入口命名为 App（create-react-app 的实现广为人知）。而 Ant Design 的 App 组件经常会和应用的 App 冲突，导致在编写代码时 （ 我的建议是，删除 Ant Design 的 App 组件，modal,message和notification通过独立的钩子和 Provider 提供： <ConfigProvider>
<MessageProvider>
<ModalProvider>
<App /> // 这是应用的 App 入口，不是 Ant Design 的 App 组件
</ModalProvider>
</MessageProvider>
</ConfigProvider>这部分其实也可以在 v5 支持。 |
Beta Was this translation helpful? Give feedback.
-
|
这个主意好，提个RFC看看维护人员态度？ |
Beta Was this translation helpful? Give feedback.
-
|
直接 HOC 现在的组件的 hooks 用法即可，App 本来就是为了便捷使用，不是强制要求。 |
Beta Was this translation helpful? Give feedback.
-
是的，如果不是为了使用方便，自己稍微包装一下即可实现Demo中的使用方式 |
Beta Was this translation helpful? Give feedback.
-
|
关于 Table 组件，经常遇到的一个场景是，希望Table组件自适应的占据页面剩余空间，同时也希望Table的头部、底部保持固定的时候，自适应的把表格内容撑大。现在不管是手动来计算高度，还是通过hack的方法覆盖css样式，总是有点麻烦的。 |
Beta Was this translation helpful? Give feedback.
-
|
个人感觉基于 HTML |
Beta Was this translation helpful? Give feedback.
-
|
guys, please at least in the version 6 we want to use our custom icons library!, maybe a mapper from ant-icons to out custom ones will be helpul, ant-icons are too basic and too squared to be used in a professional way.. |
Beta Was this translation helpful? Give feedback.
and others
-
📋 RFC
Summary
>= 18Motivation
As planed, antd will start v6 version to match with React 19. This is also a good time to get rid of legacy browser support.
Detailed
⚛️ React compatible to 18
React provide new strong hooks since 18. But to compatible with old version, antd inside use fallback logic to fullfill the hooks which may cause behavior difference between versions. And also some static method like
Modal.confirmneed the extra render ability which is not same function since 18 and can not compatible with 19 ever. So the version will be raised.🪦 Finally remove IE support
v5 removed base support but still provide fallback ability. In v6, will will fully remove IE support thus you can no longer use the legacy transform plugin to compatible with IE.
🌈 Pure css variables resolution
When deprecated IE support.
@ant-design/cssinjswill only provide css variables resolution. It will save large scale of uselessmemocomparison for dynamic style calculation.Also, css content part will support zero runtime generation which means you can use current
@ant-design/static-style-extractlib to generate framework level css and theme level css at same time. It can help to use css variable to do simplify theme switch or client fully ability for dynamic theme switch.🚫 Remove
findDOMNodeantd will fallback to use
findDOMNodewhen children not supportref. Since React 19 will traderefas normal props, we will not longer support the fallback logic withfindDOMNodeanymore.🧩 Fully semantic DOM
All the components will provider semantic
classNames&stylesprops and added in ConfigProvider, thus you can customize theme ability when design token not support:🛠️ Retire v4 deprecated API
As major release tradition. The deprecated API before 2 version will be removed.
📱 Mobile UX improvement
For the interactive, partial component with popup element will do the adjustment for compatible with mobile device screen to improve the user experience. Some component may adjust design if can not auto scale.
Adoption strategy
nextbranch which will keep sync withmaster.master.Ant Design v6 tasks
Beta Was this translation helpful? Give feedback.
All reactions