r/javascript • • 19h ago

Subreddit Stats Your /r/javascript recap for the week of October 19 - October 25, 2026

0 Upvotes

Monday, October 19 - Sunday, October 25, 2026

Top Posts

score comments title & link
116 44 comments Introducing tsrs: a Port of TypeScript to Rust
98 35 comments Announcing TypeScript 7.1 Beta
78 6 comments We just gave a million dollars to Open Source maintainers
52 29 comments I spent three years building Nanoviews, a tiny UI library on signals. It just hit 1.0
28 1 comments LittleJS Engine is 2D and 3D now
15 23 comments Wasp web framework v1.0 is coming: the roadmap and what changes
9 5 comments Inline rendering with document​.currentScript
7 7 comments [Showoff Saturday] Showoff Saturday (October 24, 2026)
6 0 comments a website that lets you play with antennas and visualize the electromagnetic field
4 0 comments DigitalVisualMixer: live visuals, no experience required

 

Most Commented Posts

score comments title & link
0 13 comments made a CLI that generates a typed client from a HAR capture β€” here's what the output looks like
0 10 comments HTML is Alive - an exhortation to remove its ventilator
0 5 comments [AskJS] [AskJS] :Recently got a PR merged into TanStack Query
0 4 comments Article: I replaced EsLint. The First Attempt Worked. I threw it away.
3 4 comments Knitting β€” a shared-memory concurrency runtime for JavaScript

 

Top Showoffs

score comment
2 /u/lbragile_dev said https://reddit.com/link/19rlo27m59x5u/video/mk6gxsvaihxh1/player [tabmerger.com](http://tabmerger.com/) [github.com/lbragile/TabMerger](http://github.com/lbragile/TabM...
2 /u/ImaginationVarious30 said Showoff: **hexvero**, a TypeScript CLI that diffs two builds of an Electron app without running either. It answers "what did this release change for the pages inside it?": new preload/contextB...
2 /u/intensityflow said made a little in-browser converter for arc's sidebar file, since arc shuts down dec 22 and its own new export saves your tabs as a list of links. you drop in StorableSidebar.json and get a normal book...

 

Top Comments

score comment
46 /u/Dramatic_Mastodon_93 said is all software devs do nowadays port stuff from one language or framework to another language or framework
38 /u/Ecksters said If I remember correctly, the reason Go was picked was because they were more easily able to translate over the code directly compared to other low level languages. Given that we have a heavy test sui...
37 /u/somebody-2027 said You gotta be kidding me. I get it, rust is great, and AI makes many new things possible. But I will NEVER us a third party typescript compiler. TS has far too many esoteric rules to trust anything not...
35 /u/queen-adreena said Yay. Finally we can get ESLint support for Typescript Go.
28 /u/Spare_Message_3607 said I see where they are going. Vite owning the whole thing, Typescript, linter, formatter, build, test. Honestly, I would say the port is completely unnecessary, Go is fast enough for most projects under...

 


r/javascript • • 2h ago

Typescript/React

Thumbnail github.com
0 Upvotes

How to make this game better ?


r/javascript • • 5h ago

A New Node.js library

Thumbnail npmjs.com
0 Upvotes

When you scale a Node.js backend using node:cluster, you run into a surprisingly annoying problem:

How do you rate-limit external APIs like Stripe or OpenAI while making sure all workers share the same rate limit?

The first solution that comes to mind is usually: "Just use Redis."

But does it really make sense to introduce additional infrastructure complexity, network overhead, and an entire external dependency just to coordinate a few API calls coming from the same server?

That's exactly why I built cluster-rate-limiter.

A Node.js library that gives you coordinated rate limiting across workers, powered entirely by Node.js's native IPC messaging, with no Redis and absolutely zero external dependencies.

Rather than diving into the internals here, here's what you get out of the box:

  • Zero Setup: Install it and start using it. No additional infrastructure required.
  • Developer-Friendly API: The run() method accepts your fetch call or any function directly, along with all its arguments. No complicated callback patterns.
  • Two Types of Limits: Supports both Semaphore-based concurrency limits and Duration-based rate limits for enforcing strict time windows, such as those imposed by Stripe APIs.
  • Typed Errors: If a request times out waiting for permission, the library throws a clear, specific error that you can easily translate into an HTTP 429 Too Many Requests response.

And when it comes to performance, the core data structure for tracking request timestamps uses a zero-allocation approach built around a Float64Array ring buffer.

This eliminates the need for repeated array reallocations and significantly reduces garbage collection pressure under heavy load.

If you're interested in the low-level details, I've explained the ring buffer implementation and how it reduces memory overhead in the README.

If you're running a clustered Node.js backend and want to avoid the overhead of introducing Redis just for rate limiting, check out the links below, explore the architecture, and let me know what you think!