You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
From the Hono document:
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?
Footnotes
https://hono.dev/docs/getting-started/deno#npm-specifier ↩
The text was updated successfully, but these errors were encountered: