Alex Kirszenberg 7bbc1aec9a Aggregate updates using addStatusHandler and Promise.resolve instead of setTimeout (#42350) ... The current `setTimeout` logic adds a constant overhead of 30ms when applying updates, which slows down HMR. As @sokra suggested, we can use the `addStatusHandler` API to have the HMR runtime let us know when its status changes. This also switches to `Promise.resolve` for update aggregation.		2022-11-07 21:06:18 +00:00
..
create-next-app	v13.0.3-canary.0	2022-11-04 16:40:57 -07:00
eslint-config-next	v13.0.3-canary.0	2022-11-04 16:40:57 -07:00
eslint-plugin-next	v13.0.3-canary.0	2022-11-04 16:40:57 -07:00
font	Fix replaceAll usage in font loader (#42550)	2022-11-06 15:23:02 -08:00
next	Aggregate updates using addStatusHandler and Promise.resolve instead of setTimeout (#42350)	2022-11-07 21:06:18 +00:00
next-bundle-analyzer	v13.0.3-canary.0	2022-11-04 16:40:57 -07:00
next-codemod	v13.0.3-canary.0	2022-11-04 16:40:57 -07:00
next-env	v13.0.3-canary.0	2022-11-04 16:40:57 -07:00
next-mdx	v13.0.3-canary.0	2022-11-04 16:40:57 -07:00
next-plugin-storybook	v13.0.3-canary.0	2022-11-04 16:40:57 -07:00
next-polyfill-module	v13.0.3-canary.0	2022-11-04 16:40:57 -07:00
next-polyfill-nomodule	v13.0.3-canary.0	2022-11-04 16:40:57 -07:00
next-swc	v13.0.3-canary.0	2022-11-04 16:40:57 -07:00
react-dev-overlay	Aggregate updates using addStatusHandler and Promise.resolve instead of setTimeout (#42350)	2022-11-07 21:06:18 +00:00
react-refresh-utils	Aggregate updates using addStatusHandler and Promise.resolve instead of setTimeout (#42350)	2022-11-07 21:06:18 +00:00