Also publish to JSR?

[imcotton]

From the Hono document:

If you want to use Third-party Middleware with the TypeScript Type inferences, you need to use the npm: specifier. ^deno

For package like npm:@hono/valibot-validator, this holding my back from using Hono from JSR by:

• jsr:@hono/hono
• jsr:@valibot/valibot

Any plans to have middleware packages also available on JSR too?

[yusukebe]

Hi @imcotton

Supporting JSR is great. But there are some reasons I can't do it now:

• Making them support JSR will be hard. Especially removing slow types.
• Have to create deploy flow. I'm unsure if we can create a good flow to publicize them with Changesets.
• Maintenance costs will be increased. We(almost I) must also check the JSR things by adding npm packages.

[imcotton]

I think slow types is OK-ish for just publish with --allow-slow-types if it cost too much of effort.

Flow-wise, I think it'd be done by:

• having one corresponding jsr.json file
• add deno publish or npx jsr publish right after the npm publish on its CI

Maintenance indeed increased, but if I'm not missing anything else, above only be one time setup per package and then automatically carried afterwards.

Not sure the jsr:@hono/* is the intended place to publish these middleware, but right now it rather empty since only hosting the jsr:@hono/hono and nothing else.

I understand this is low priority and still up to decisions, in the meantime I could vendor the TypeScript source code by coping into my own project, but thought it worth to brought up to discussion, thanks for the participation.

[ingokpp]

+1 For JSR support. I really like the idea of not using npm at all in my deno project.

[dmint789]

+1 too. Would be nice to have the @hono/zod-validator package on there.