ba252d8765
It _might_ be an overhead to send over a large amount of data over `postMessage` just for diff. HMR and module compilation is way less frequent than evaluation in the sandbox, so maybe we should always invalidate the cache eagerly without any comparison and defer the workload to `evaluateInContext`. Some observations: <img width="662" src="https://github.com/vercel/next.js/assets/3676859/12136002-8857-4e10-ba9a-bf420d098dc8"> <img width="662" alt="CleanShot 2023-06-28 at 08 26 23@2x" src="https://github.com/vercel/next.js/assets/3676859/db054948-a0ea-4d98-bf4f-aa125e0eb1b5"> ![CleanShot 2023-06-28 at 08 02 24@2x](https://github.com/vercel/next.js/assets/3676859/b674beb1-d53c-4a1d-a9bf-ca3672e089c8) |
||
---|---|---|
.. | ||
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 |