Cannot resolve *.module.css using paths of tsconfig.json

[mizdra]

css-modules-kit uses paths to resolve import specifiers.

However, there are several edge cases that fail to resolve.

Case 1

One of these is Go to Definition in ts-plugin. Go to Definition fails if user clicks on import specifier with paths.

2025-03-01.18.32.25.mov

Case 2

Another is when the type definition file generated by codegen is type-checked by tsc.

// src/a.module.css
@import '@/d.module.css';

// src/d.module.css
.d_1 { color: red; }

// generated/a.module.css.d.ts
// @ts-nocheck
declare const styles = {
  ...(await import('@/src/d.module.css')).default,
  //                ^^^^^^^^^^^^^^^^^^
  //                This import speficier cannot be resolved by tsc.
  //                Therefore, the `(await import(...)) .default)` will be `any` type.
  //                Worse, `styles` will also be of `any` type.
};
export default styles;

Since styles will be any type, a type error will not be reported if you reference a non-existent class name from *.ts.

// src/a.ts
import styles from './a.module.css';
styles.unknown; // This should be reported as a type error

$ npx tsc
$ echo $?
0

Additional Information

The problem appears to be due to the following TypeScript behavior.

• Support go-to-definition on tsconfig mapped paths for non-source files microsoft/TypeScript#44564