Ok, seems like .d.ts is actually generated - but because of the issue mentioned here I was thinking that I was looking at another directory (the root entry).

I feel however that maybe it should be validated that "types" got used and throw an error on that (in favor of those type files that are auto-generated). This should ofc happen only for TS projects - adding "types" manually should be supported for packages shipping .d.ts without them actually being written in TS.

I feel however that maybe it should be validated that "types" got used and throw an error on that (in favor of those type files that are auto-generated). This should ofc happen only for TS projects - adding "types" manually should be supported for packages shipping .d.ts without them actually being written in TS.

Agreed

Hey folks, what's the status of "types" field in package.json with Preconstruct? (BTW Preconstruct is blazing fast. Wow.)

TypeScript docs advise to add "types" key to package.json. Should preconstruct fix add it to point to the generated .cjs.d.ts file?

There's no real need since TypeScript can already resolve it. Is there are a particular reason you want to add it to the package.json?

Even to make it easier for other tools. For example, npm marks packages with TS types with a special badge. Compare:

• https://www.npmjs.com/package/@changesets/git
• https://www.npmjs.com/package/xstate

Is there are a particular reason you want to add it to the package.json?

What Andarist said, and I vaguely remember PRing/patching niche libraries I wanted to use, because old TS couldn't resolve it.

Okay, sounds good. Happy to accept a PR adding this(behind a flag for now because it would be a breaking change otherwise)