Do not use export = in TypeScript declaration files

[dsherret]

TypeScript may start raising a diagnostic when ESM declaration files use export =. This will cause issues for esm.sh. For example: https://esm.sh/@types/[email protected]/index.d.ts serves up a declaration file that has export = santize in it. I think export = needs to be moved away from.

See microsoft/TypeScript#51321 (comment) for more details.

[ije]

thanks! i will look into it.

[ije]

@dsherret should we rename export = santize to export default santize or just remove it?

[dsherret]

It should represent the transformed esm code, so I think export = should go to export default? Maybe that doesn't always work easily.

[ije]

The testing is failed after resolving export = to export default, i will figure out

[ije]

rename export = or remove it, both break some types, i reverted for now

[dsherret]

This diagnostic has now landed in TypeScript 5.0. export = is being denied in ambient declaration files. I'm going to change the typescript source in Deno to temporarily allow it though.

[dsherret]

This is going to start erroring in Deno 2.0 in order to align with TypeScript as it doesn't make sense for an esm module to have a common js export = microsoft/TypeScript#52109

[ije]

thnaks @dsherret i will look into it!

[dsherret]

It should be warning now in the latest RC. It might start erroring sometime in the future, but I'm not sure how feasible that is to do.