CRITICAL: description on `noUncheckedSideEffectImports` has no guide for CSS npm library authors to have users avoid TS2882 when import css globally

Page URL: https://www.typescriptlang.org/tsconfig/#noUncheckedSideEffectImports https://www.typescriptlang.org/docs/handbook/release-notes/typescript-6-0.html

Issue:

TS 6.0 turned on noUncheckedSideEffectImports by default but it causes errors on CSS libraries meeting the following conditions:

• Has entrypoints meeting the following conditions:
  • Their names don't end with .css (e.g. library-name/css)
  • Globally imported (import "library-name/css")
  • Doesn't have "types" fields in their "exports" fields in package.json

Library users bump into TS2882 at import "library-name/css".

• https://github.com/payloadcms/payload/issues/16346
  • https://github.com/payloadcms/payload/commit/6c81355a8d2cc822d9e4484105d53888a5fa9444
• https://github.com/tauri-apps/meilisearch-docsearch/issues/219
• https://github.com/vuetifyjs/vuetify/issues/22766
  • https://github.com/vuetifyjs/vuetify/commit/2098fb180ea83ed1d35df10d2132c9157a37079a
• https://github.com/arnog/mathlive/issues/3030
• https://github.com/search?q=noUncheckedSideEffectImports+TS2882+import&type=issues

The offending pages must provide a guide for CSS library authors to deal with noUncheckedSideEffectImports.

Start with the noUncheckedSideEffectImports section and the linked TypeScript 6.0 release notes page, then review the listed TS2882 and CSS package cases. Done means both affected pages explain how CSS library authors can help users avoid TS2882 when users globally import CSS entrypoints.