[code-infra] Setup error message minification

[Janpot]

Port core error minification infrastructure:

• Built on top of [code-infra] Allow specifying a custom error formatter module for error minifcation material-ui#45291
• Add error extractor in babel
• Extract all errors, make the behavior opt-out with

  throw /* minify-error-disabled */ new Error('unminified error message');

• Remove unused babel macros plugin
• Add production-error page in the docs, use <FormattedErrorMessage /> inside of the mdx to render the formatted error message
  • Statically prerenders all pages for errors. The args are passed through searchParams so they can only be interpolated client side.
• example
• example with inerpolation

[netlify]

✅ Deploy Preview for base-ui ready!

Name	Link
🔨 Latest commit	8fa10ed
🔍 Latest deploy log	https://app.netlify.com/sites/base-ui/deploys/67dbe7a32851500008f625c4
😎 Deploy Preview	https://deploy-preview-1463--base-ui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[michaldudak]

It looks good, aside from a typo I found.
@atomiks, do you see anything missing from this implementation?

In the future, we could create an error throw helper function to ensure consistency in our messages.
I'm wondering how big the bundle size savings will be and if the minification is really worth the hassle.

[Janpot]

I'm wondering how big the bundle size savings will be and if the minification is really worth the hassle.

Ideally we'd have the bundle size checker in base repo. I can fix that up and port next? We could also postpone merging this PR until then if you want,

[michaldudak]

I checked it manually and it turns out that this PR (with the lastest master merged in) produces a larger package than what's on master.

I ran pnpm build and pnpm pack in the package directory with the following results:

This PR:
package (tgz): 332555 bytes
esm directory (unpacked): 1315505 bytes

master:
package (tgz): 329511 bytes (3044 bytes less)
esm directory (unpacked): 1307340 bytes (8165 bytes less)

I expect it to look different when we add more components and have more error messages, but for now there seems to be no point in making this change (unless my methodology is wrong).

We can also have additional gains in the minifier-less implementation by creating the error helper I mentioned in #1463 (review)

[Janpot]

(unless my methodology is wrong)

The installed size will indeed be larger as it contains a new function and the error codes alongside the dev messages. But that's not what ends up in user's applications. You need to bundle the package with process.env.NODE_ENV set to 'production' and check the result. That's why I proposed we clean up and port the bundle size checker from core.

[Janpot]

Putting this on hold until we've ported the bundle size checker and can assess the impact.