Show HN: I rewrote an outdated React Native map clustering library
Hacker News (score: 22)Description
I'm a long-time lurker and wanted to share a project I just finished building.
Like many React Native developers, I needed to add marker clustering to a map in my app. The most popular library for this, react-native-maps-clustering, was fantastic in its day but has become outdated and no longer works with modern versions of Expo, React Native, and their dependencies.
After hitting a wall of compatibility issues, I decided to take on the challenge of rewriting it from the ground up, focusing on a modern toolchain and a better developer experience.
The journey was a lot more challenging than I anticipated. It turned into a deep dive into solving dependency hell with different versions of @types/react, wrestling with build tool configurations for pnpm, bob, and ESLint, and ensuring everything was strictly typed with TypeScript. It felt like a classic case of yak shaving, but I was determined to create a solution that "just works" for developers today.
The result is RN Super Cluster, a performant, fully-typed, and easy-to-use clustering library for react-native-maps.
What it does: It provides a <ClusteredMapView /> component that you can use as a drop-in replacement for the standard <MapView />. Any <Marker /> components you place inside will be automatically clustered.
Key Features:
Modern & Maintained: Built with a modern toolchain and designed to be actively maintained.
Fully-Typed: Written entirely in TypeScript to prevent common errors and improve autocompletion.
High-Performance: Uses supercluster under the hood for extremely fast geospatial clustering.
Spiderfier: At the maximum zoom level, overlapping markers automatically "spiderfy" (spread out on a spiral) so they can be individually tapped.
Customizable: You can provide your own custom components for rendering clusters, and callbacks for handling press events.
This was a passion project born out of necessity, and I hope it can save other React Native developers the headaches I went through.I would love to get your feedback, and contributions are more than welcome!
GitHub: https://github.com/suwi-lanji/rn-maps-clustering NPM: https://www.npmjs.com/package/rn-maps-clustering
Thanks for checking it out!
More from Hacker
Show HN: Hc: an agentless, multi-tenant shell history sink
Show HN: Hc: an agentless, multi-tenant shell history sink This project is a tool for engineers who live in the terminal and are tired of losing their command history to ephemeral servers or fragmented `.bash_history` files. If you’re jumping between dozens of boxes, many of which might be destroyed an hour later, your "local memory" (the history file) is essentially useless. This tool builds a centralized, permanent brain for your shell activity, ensuring that a complex one-liner you crafted months ago remains accessible even if the server it ran on is long gone.<p>The core mechanism wants to be a "zero-touch" capture that happens at the connection gateway level. Instead of installing logging agents or scripts on every target machine, the tool reconstructs your terminal sessions from raw recording files generated by the proxy you use to connect. This "in-flight" capture means you get a high-fidelity log of every keystroke and output without ever having to touch the configuration of the remote host. It’s a passive way to build a personal knowledge base while you work.<p>To handle the reality of context-switching, the tool is designed with a "multi-tenant" architecture. For an individual engineer, this isn't about managing different users, but about isolating project contexts. It automatically categorizes history based on the specific organization or project tags defined at the gateway. This keeps your work for different clients or personal side-projects in separate buckets, so you don't have to wade through unrelated noise when you're looking for a specific solution.<p>In true nerd fashion, the search interface stays exactly where you want it: in the command line. There is no bloated web UI to slow you down. The tool turns your entire professional history into a searchable, greppable database accessible directly from your terminal.<p>Please read the full story [here](<a href="https://carminatialessandro.blogspot.com/2026/01/hc-agentless-multi-tenant-shell-history.html" rel="nofollow">https://carminatialessandro.blogspot.com/2026/01/hc-agentles...</a>)
Show HN: Ayder – HTTP-native durable event log written in C (curl as client)
Show HN: Ayder – HTTP-native durable event log written in C (curl as client) Hi HN,<p>I built Ayder — a single-binary, HTTP-native durable event log written in C. The wedge is simple: curl is the client (no JVM, no ZooKeeper, no thick client libs).<p>There’s a 2-minute demo that starts with an unclean SIGKILL, then restarts and verifies offsets + data are still there.<p>Numbers (3-node Raft, real network, sync-majority writes, 64B payload): ~50K msg/s sustained (wrk2 @ 50K req/s), client P99 ~3.46ms. Crash recovery after SIGKILL is ~40–50s with ~8M offsets.<p>Repo link has the video, benchmarks, and quick start. I’m looking for a few early design partners (any event ingestion/streaming workload).
Useful patterns for building HTML tools
Useful patterns for building HTML tools
Migrating to Positron, a next-generation data science IDE for Python and R
Migrating to Positron, a next-generation data science IDE for Python and R
No other tools from this source yet.