Hono v4.0.0

• hono

  73 20,832 9.8 TypeScript

  Web framework built on Web Standards

  

  > https://github.com/honojs/hono

  > About: Fast, Lightweight, Web-standards

  Okay...

  > hono.dev

  > Fast, Lightweight, Web-standards

  > Runs on any JavaScript runtime.

  ???

  > Ultrafast & Lightweight

  > The router RegExpRouter is really fast. The hono/tiny preset is under 14kB. Using only Web Standard APIs.

  Oh I guess maybe this is a http server?

• CodeRabbit

  coderabbit.ai featured

  CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

  

• h3

  10 3,746 9.2 TypeScript

  ⚡️ Minimal H(TTP) framework built for high performance and portability (by unjs)

  

  Same, I'll probably move to https://github.com/unjs/h3 since it's used anyway in Nuxt (which I use for other projects)

• llrt

  14 8,167 9.7 JavaScript

  LLRT (Low Latency Runtime) is an experimental, lightweight JavaScript runtime designed to address the growing demand for fast and efficient Serverless applications.

  

• sst

  185 22,309 10.0 TypeScript

  Build full-stack apps on your own infrastructure.

  

  > But if you have a sufficiently large enough API surface, doing one lambda per endpoint comes with a lot of pain as well. Packaging and deploying all of those artifacts can be very time consuming, especially if you have a naive approach that does a full rebuild/redeploy every time the pipeline runs.

  Yeah, thankfully SST [0] does the heavy lifting for me. I've tried most of the solutions out there and SST was where I was the happiest. Right now I do 1 functions per endpoint. I structure my code like url paths mostly, 1 stack per final folder, so that the "users" folder maps to "/users/*" and inside I have get/getAll/create/update/delete files that map to GET X/id, GET X, POST X, POST X/id, DELETE/id. It works out well, it's easy to reason about, and deploys (a sizable a backend) in about 10min on GitHub Actions (which I'm going to swap out probably for something faster).

  I agree with the secrets/permissions aspect and I like that it's stupid-simple for me to attach secrets/permissions at a low level if I want.

  I use NodeJS and startup isn't horrible and once it's up the requests as very quick. For my needs, an the nature of the software I'm writing, lambda makes a ton of sense (mostly never used, but when it's used it's used heavily and needs to scale up high).

  [0] https://sst.dev

Suggest a related project