Enjoy the launch!

Would you use @heyapi.dev if I publish it?

Does anyone use @deno.land?

I didn’t think otherwise but you saying it makes me suspicious now

Does anyone use @jsr.io? Is it worth setting up a distribution pipeline to their registry?

Thank you! Also for contributing towards that count

They say the first million is the hardest. It’s true.

Feel free to drop by GitHub if you ever have any feedback!

Oh, are you using it? From Unity times or did you discover it more recently?

Bluesky is pretty dead in general, but at least the comments you receive are human, unlike Twitter

I don’t get what it represents. One of those packages has 2 releases in 6 months but you’d never guess which one. It’s not like it’s a complete project either, it has a ton of open issues. How would you balance a “done” solution vs something new in active development anyway? This shouldn’t exist imo

There are larger packages because they do more, packages that can be tree-shaked to be smaller, and larger packages with faster runtime performance. Bundle size matters mostly on the client anyway, assuming it’s not a devDependency like my example. This feature just isn’t helpful and should be gone

Assuming you suggest smaller install size = better, encourage ESM over CJS, you must be overindexing on dependencies or aggregating stats from them too because this feels very wrong. If you ask actual people or LLMs, they wouldn’t plot it like this.

I don’t understand ergonomics (install size, dependencies, vulnerabilities, type support).

“Use vi.mock when you want fast, isolated unit tests with precise control over return values.”

Any sense of how much faster it is? As for the precise control argument I don’t buy it, MSW offers the same.

So… your package is taken?

Technically both correct

Thank you for the added points! I have the benefit of working on some of this stuff as you know, and point 3 is going to be a non-issue imo, especially for existing projects.

What are some of the merits of Nock compared to MSW?

I was pleasantly surprised to see Sascha recommend Hey API over alternatives because there's still a lot of work to do!

What do those people who complain do instead?

Thanks to Yuri, Hey API is the only major code generator with NestJS support.

It’s annoying but it made me realize I was opted in so

Do you have any helpful articles about dev containers?

Are you as bullish as ever? Haven’t been keeping up with this name

Appreciate you guys!

Appreciate it!

@hey-api/openapi-ts - npmx 🌀 OpenAPI to TypeScript codegen. Production-ready SDKs, Zod schemas, TanStack Query hooks, and 20+ plugins. Used by Vercel, OpenCode, and PayPal.

If you’re using the new npm website, please leave openapi-ts a like! npmx.dev/package/@hey...