modern-normalize

It was not included in the initial PR, as per this blog post, it's not yet safe to use. We need to move on soon though, as Chrome plans to deprecate the font name, per https://github.com/sindresorhus/modern-normalize/pull/16#issuecomment-364504396. Also see: https://github.com/primer/primer/pull/408

Counter to the common trend, it is _not_ always 'awesome' or 'FTW'. It wreaks havoc with expectations stemming from normal browser defaults, which makes it harder to integrate into existing properties and makes it harder to integrate anything created by third parties that are not operating off of the same opinionated principle. It's also a total pain in the ass to selectively undo with override rules, as it's reapplied on every element. At the very least you could use I'd think, which makes it at least _somewhat_ easier to selectively cut this awesomely annoying behavior out?

see https://css-tricks.com/inheriting-box-sizing-probably-slightly-better-best-practice/. Even Paul Irish, original author of the fix currently part of modern-normalize, has agreed on this and edited his origjnal post back from 2021: https://www.paulirish.com/2012/box-sizing-border-box-ftw/ This will also fix https://github.com/sindresorhus/modern-normalize/issues/48.