5ad1b77704
Noticed this optimization when debugging something else - we restart this worker if it's not fresh, to make sure module instances are new created. This has some perf overhead and it happens right before running the task and it's blocking the request. This PR changes that to be after the old task, and the difference is noticeable on dev (~20ms). Before: <img width="1363" alt="CleanShot-2023-03-30-jTT9W48H@2x" src="https://user-images.githubusercontent.com/3676859/228965542-e0d6892f-3989-4da5-96a4-5fc8b4155041.png"> After: <img width="1363" alt="CleanShot-2023-03-30-PRrYQMg7@2x" src="https://user-images.githubusercontent.com/3676859/228965566-42e04f8d-0cc3-447c-adc8-3840b23b9fa5.png"> |
||
---|---|---|
.. | ||
create-next-app | ||
eslint-config-next | ||
eslint-plugin-next | ||
font | ||
next | ||
next-bundle-analyzer | ||
next-codemod | ||
next-env | ||
next-mdx | ||
next-plugin-storybook | ||
next-polyfill-module | ||
next-polyfill-nomodule | ||
next-swc | ||
react-dev-overlay | ||
react-refresh-utils |