RFC: Exportable types

[penalosa]

RFC: Exportable types

[penalosa]

@GregBrimble

1. No, because a class is both a type and a value, whereas const Response = globalThis.Response is just a value. To get the type of Response, you'd need to use typeof Response, which breaks the usual expectation for classes. That's an okay tradeoff for functions, because you need typeof for functions anyway (I'm pretty sure, at least).
2. Yes, this would be just another option

[GregBrimble]

Does Frankenstein's approach work for the other types as well? Any reason not to do that and be consistent on everything?

[GregBrimble]

Additionally, can we keep the global types for those that want to continue using workers-types in the v2 way?

[penalosa]

If we publish an ambient index.d.ts and an importable index.ts, existing code should keep working, and you'll also be able to import. Something to consider (cc @mrbbot), do we also want to try and publish to a @types/cloudflare-workers or something like that?

[GregBrimble]

Hey @jacob-ebey, we're thinking about publishing importable Workers runtime types, as well as continuing to offer the global types. Do you have any thoughts on this? Would there be interest in using the importable types in the Remix packages/templates? Or does it make sense only for users to use directly themselves?

[mrbbot]

We should be able to close all these issues if we do this:

• #164
• #195
• #199
• #203

[mrbbot]

I'm going to close this, as you can now import type { ... } from "@cloudflare/workers-types" as of @cloudflare/workers-types version 4.