build: deno support with denoify

[scarf005]

• blocked by build: bump hono to 3.4.0, @ts-rest/core to 3.27.0 #10 , feat: validate request headers #13
• resolves deno support #9

I've explicitly committed deno_dist directory following github.com/honojs/hono. By adding webhooks to deno 3rd party packages repository, this package could also be served from https://deno.land/x.

[msutkowski]

@scarf005 I know roughly 0 things about denoify :). Does the denoify step need to be a part of a build step on publish, or does this just magically work as-is?

[scarf005]

it could be either

• automated using workflow (i.e push to deno branch) to keep commit history clean, takes some work
• or be ran and updated manually using npm run denoify command.

[msutkowski]

it could be either

• automated using workflow (i.e push to deno branch) to keep commit history clean, takes some work
• or be ran and updated manually using npm run denoify command.

Yea, looking through the example here - https://github.com/garronej/my_dummy_npm_and_deno_module, there is a little more that could be done re: tsconfig, setting "build": "pkgroll && denoify", etc etc. I'm assuming it makes sense to build + publish to deno.land as a part of the normal build step? I'd be happy to just throw the publish step in CI, but could use help with any of the deno parts =)

[msutkowski]

github.com/honojs/hono

Yea, we can just do what hono does and that should be fine - https://github.com/honojs/hono/blob/main/package.json#L27-L33. If you're on discord and would like to chat about this quickly, my username is the same (msutkowski). I'd like to get this + the other open PR in and update docs + cut a release today.