suggestion: Add Deno support

[DjDeveloperr]

Hi!

After seeing comment in Pull Request in Discord API Docs repo for adding Deno support (discord/discord-api-docs#2401 (comment)), I decided to try this out.

From what I know, only import/export style has changed in Deno which makes this incompatible, which does not have anything like index.js/ts file and always requires extension of file to be in import.

I've made a script which goes through all files and makes imports/exports compatible with Deno, https://github.com/DjDeveloperr/denoify-dapi-types. There's even a working GitHub action which deploys on deno branch on every push.
You can see live version on my fork of this repo, https://github.com/DjDeveloperr/discord-api-types.

I have tested, those auto-generated types do work with Deno 😄

[advaith1]

The modified version should be compatible with both node and deno, right? Can't we just add /index.ts to the imports in the main branch to have a simple version compatible with both?

[DjDeveloperr]

I'm pretty sure if adding .ts in imports is incompatible with TypeScript (Node).

Edit: There's a plugin for TS to allow extension if I remember correctly.

[iCrawl]

microsoft/TypeScript#37582

[vladfrangu]

I mean, personally, I'm willing to create a CD that deploys to a deno branch for the time being, fast enough! What do you think, @iCrawl, @kyranet?

[kyranet]

I personally have no issue with that. the question is... how are we going to transform the imports to support Deno?