csr632
在Chome的最新版本（106.0.5249.103），性能问题似乎已经被Chrome解决了。。。
You can checkout my idea: [react-hook-svs](https://github.com/csr632/react-hook-svs). Highlights: - Get service output immediately in the hosting component. You no longer need to wrap your top component with provider HOC to get...
Agreed. "New props" is confusing and doesn't have any (correct) meaning. "Parent rerenders" give infomation about "why" and "when", just like the "setState()" and "forceUpdate()" labels do.
Yes, if the `proxy` feature or the `historyApiFallback` feature is enabled, `http-proxy-middleware` will be applied to the express server multiple times.
谢谢大佬分享！文章对我有很多启发！我想和您讨论一下： 文章里面的讨论好像是基于一个前提：“一个时刻只有**一个**应用接管**整个**页面”。请问有没有多应用共存的方法呢？比如顶栏是团队A开发的（使用Angular），侧栏是另一个团队B开发的（使用React15+antd2.x），某个弹窗是团队C开发的（使用React16+antd3.x）。 update：刚刚才发现最后一张图片有一个词“子应用并行”，可是前面讨论的“Dynamic Stylesheet ”样式隔离应该还不能支持并行吧。js隔离方案似乎是“上下文切换”，没有支持并行的应用。
Yes I will support this in a week.
> Would you support this in v3 too？ Sorry. I can't maintain two branches. You should migrate to react-router-dom v6.
Sorry I was busy with other thing and forgot this feature request. Do you still need this? I will try implementing this when I have time.
Ideally we should drop `resolveFrom` entirely and always use `tryNodeResolve`. But I feel `tryNodeResolve` very complicated and subtle to use... Callers have to collect arguments carefully and know every edge...
> Thanks for working on this regerssion! I think that if you confirmed the linked PR was causing the issue in solid we should revert it while you check this....