Any way to generate Typescript `.d.ts` declaration files instead of `.ts`?

Question

Any way to generate Typescript `.d.ts` declaration files instead of `.ts`?

Closed this issue a year ago · 9 comments

Thanks in advance!

Answer 1 · 2023-02-24T15:39:08.000Z

I guess not with the current setup, no. Can I ask a bit about the use case? Why is this necessary? Are you using any enums?

Answer 2 · 2023-02-27T23:36:52.000Z

One of the use cases is that it allows the type definitions to be used in purely js modules. Plus, it semantically makes sense to have all the type definitions of a project in type declaration (.d.ts) files.

Answer 3 · 2023-03-01T15:24:13.000Z

Yeah, I can see how that makes sense. What would you suggest in the case of enums? Should they be disallowed with this option?

Answer 4 · 2023-03-03T17:45:52.000Z

That's a good point. Honestly I don't have enough information on this but maybe this could be a solution.

Answer 5 · 2023-07-26T08:43:36.000Z

| chaining for Enums is what I've seen done in other tooling like the graphql "codegen".

Answer 6 · 2023-07-26T10:33:18.000Z

@karloluis I am not sure I follow. How do you use the pipe operator with enums?

Answer 7 · 2023-07-26T12:19:59.000Z

Instead of typing enums as the enum Vals { value1, value2 } it will instead be type Vals = 'value1' | 'value2'

Answer 8 · 2023-07-26T12:47:37.000Z

Ah right. That's possible by setting enumStyle to type for unions. I was considering making this the default as I greatly prefer unions over enums, but enums have the one upside that items can have comments.

Answer 9 · 2024-07-18T10:17:22.000Z

For future readers, you might not need this, TypeScript appears to be happy with packages that just do "types": "./dist/index.ts", index.ts being generated by generateIndexFile pre-render hook.