Hey 👋🏻
Nikos from Clerk here. Congrats on the State of JS 2025 results - well deserved! It's been great watching Hono's growth. We're big fans at Clerk - we use Hono in our Cloudflare Workers, and I personally use it in a couple of side projects as well.
We're planning to move the @hono/clerk-auth package to our monorepo as @clerk/hono as we want to offer official first-party support going forward.
Why
The main reasons for the move:
- Faster iteration - our monorepo is using PNPM workspaces and the
workspace:* protocol for managing Clerk dependencies. Right now the Hono middleware can lag behind since it lives in a separate repo and all updates need to happen sequentially (update Clerk packages -> release -> update @hono/clerk-auth -> verify -> release).
- Better support - users filing issues in our repo means our team can triage and respond directly.
Migration
We're keeping the public API identical - clerkMiddleware, getAuth, same options, same behavior. For users, migration will look like:
npm install @clerk/hono
npm uninstall @hono/clerk-auth
And updating imports from @hono/clerk-auth to @clerk/hono. That's it.
We'll continue to backport any security patches to @hono/clerk-auth until the next major release, so there's no rush for users to migrate immediately of course.
For context, @octoper who wrote the original package and @wobsoriano who's been maintaining it since are Clerk engineers - they are are ready to lead the official support effort as well :)
Happy to add a deprecation notice to @hono/clerk-auth pointing users to @clerk/hono, or help with any coordination needed.
Please let us know if you have any questions, concerns or you want to handle the migration differently!
Cheers,
Nikos
Hey 👋🏻
Nikos from Clerk here. Congrats on the State of JS 2025 results - well deserved! It's been great watching Hono's growth. We're big fans at Clerk - we use Hono in our Cloudflare Workers, and I personally use it in a couple of side projects as well.
We're planning to move the
@hono/clerk-authpackage to our monorepo as@clerk/honoas we want to offer official first-party support going forward.Why
The main reasons for the move:
workspace:*protocol for managing Clerk dependencies. Right now the Hono middleware can lag behind since it lives in a separate repo and all updates need to happen sequentially (update Clerk packages -> release -> update@hono/clerk-auth-> verify -> release).Migration
We're keeping the public API identical - clerkMiddleware, getAuth, same options, same behavior. For users, migration will look like:
And updating imports from
@hono/clerk-authto@clerk/hono. That's it.We'll continue to backport any security patches to
@hono/clerk-authuntil the next major release, so there's no rush for users to migrate immediately of course.For context, @octoper who wrote the original package and @wobsoriano who's been maintaining it since are Clerk engineers - they are are ready to lead the official support effort as well :)
Happy to add a deprecation notice to
@hono/clerk-authpointing users to@clerk/hono, or help with any coordination needed.Please let us know if you have any questions, concerns or you want to handle the migration differently!
Cheers,
Nikos