mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-11-22 18:00:18 +01:00
e951fe6a64
On an M1 Mac, when running `yarn start`, CPU can spike to 100% CPU, and sometimes a bunch of `mdworker` instances will get spawned. This seems to be caused by the file-watching mechanism used in dev to automatically regenerate the build when something is changed. More specifically, we are using an older version of `watchify`, which uses an older version of `chokidar`, which is the package that actually does the watching. v4.0.0 of `watchify` upgrades `chokidar` to v3.x ([1]), which comes with "massive CPU & RAM consumption improvements" ([2]). After the upgrade, CPU usage decreases to 20-40%. [1]: https://github.com/browserify/watchify/blob/master/CHANGELOG.md#400 [2]: https://github.com/paulmillr/chokidar/releases/tag/3.0.0 |
||
|---|---|---|
| .. | ||
| @formatjs+intl-utils+3.3.1.patch | ||
| abort-controller+3.0.0.patch | ||
| combine-source-map++convert-source-map+1.1.3.patch | ||
| error+7.0.2.patch | ||
| fast-json-patch+2.2.1.patch | ||
| gulp-sourcemaps+3.0.0.patch | ||
| inline-source-map+0.6.2.patch | ||
| luxon+1.26.0.patch | ||
| plugin-error+1.0.1.patch | ||
| regenerator-runtime+0.13.7.patch | ||
| sass+1.32.4.patch | ||
| selenium-webdriver+4.0.0-alpha.7.patch | ||
| squirrelly+8.0.8.patch | ||
| stylelint+13.6.1.patch | ||
| undeclared-identifiers+1.1.2.patch | ||
| watchify+4.0.0.patch | ||
| web3+0.20.7.patch | ||