Michael Loughry

@tancredi, would love a review on this one-line fix. Currently, `fantasticon` doesn't correctly support code points greater than 0xFFFF, because [`String.prototype.charCodeAt()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/charCodeAt) only supports UTF-16 code points, whereas [`String.prototype.codePointAt`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/codePointAt) supports all...

The zip archive is about 4MB, and unzipped it’s about 6MB.

Ok, scratch that last comment. Another dev pointed out it could be one of the package’s dependencies, and it turns out that it was: a localized strings package that is...

We were already using `compressionLevel: 0` ```.yarnrc.yml compressionLevel: 0 enableGlobalCache: true nodeLinker: node-modules npmAlwaysAuth: true npmRegistryServer: yarnPath: .yarn/releases/yarn-4.0.2.cjs ``` Unfortunately, the changes in #6011 did not resolve the issue.

Of note, the current alpha of `webpack` drops support for automatic NodeJS polyfills, so I'm running into this issue testing out their alpha. https://github.com/webpack/changelog-v5/blob/master/README.md#automatic-nodejs-polyfills-removed > ## Automatic Node.js Polyfills Removed...

For some real-world data from Outlook Web's codebase, I ran both v5-alpha.6 and this branch in dev watch mode 5 times each, and triggered 5 incremental builds for each run....

This change is an incredible win for build performance on our project. Even if it's purely opt-in, I'm really looking forward to it.