• You have only a few CSS imports.
• You want stricter module declarations.
• You want TypeScript to catch more invalid CSS paths.
• You are maintaining a library with carefully controlled imports.

For a typical Next.js application with multiple third-party packages, however, the wildcard approach is generally more convenient.

Recommended Configuration for Next.js

If you're using Next.js and encounter:

TS2882: Cannot find module or type declarations for side-effect import

and the problematic import is a CSS file, start with:

global.d.ts

declare module '*.css' {}

Then make sure the file is included in your TypeScript project.

For example:

tsconfig.json

{
  "include": [
    "global.d.ts",
    "src/**/*.ts",
    "src/**/*.tsx"
  ]
}