Heuristics for generating and specifying .d.ts files in package.json

[grenierdev]

I have a collection of six packages available at jsr.io/@baseless. Currently, some of these packages, like @baseless/core and @baseless/react, lack generated .d.ts files.

When importing @baseless/react into a react app, it seems like TSC loads the types from .ts. Since these files are in the package, but referencing jsr:@baseless/client, TSC resolves my types to any.

Could you provide guidance or heuristics for ensuring .d.ts files are correctly generated and referenced in package.json?

[grenierdev]

Seems like it all boils down to "slow types" being ignored.

Due to their nature of affecting if JSR can understand the code, you can not selectively ignore individual diagnostics for slow types. Slow type diagnostics can only be ignored for the entire package. Doing this results in incomplete documentation and type declarations for the package, and slower type checking for consumers of the package.

- Ignoring slow types

I fixed my slow types in @baseless/react and published it again and the d.ts were there.