Find what version of your package is used in a given repository.
To start the development server, run:
bun run devOpen http://localhost:3000/ with your browser (if it has a nice JSON renderer)
to see the result, otherwise curl + jq:
curl https://version-crawler.47ng.com/TheOrcDev/8bitcn-ui/nuqs | jq '.'I built a service (not yet OSS, will be soon) to fetch a leaderboard of the most popular OSS repos that use nuqs.
Keeping track of star counts & repository metadata is simple enough, but I wanted to also know what version of nuqs they were using, to identify patterns and opportunities to open PRs to upgrade older versions (especially for sponsors).
The GitHub code search API has very strict rate limits (10 req/min), meaning it would take 5 hours to go over the ~3000 dependents I have on record.
Instead of brute-force code search (which can lead to false positives), I wanted to try another way:
- Get a recursive tree for the given repo using the GitHub API
- Identify relevant files (
package.json& lockfiles) - Fetch those from the GitHub public CDN
- Extract the nuqs version(s) information
- Provide a link back to that line in the file
This allows getting high-fidelity results, without AI, and in a single API call.
But really, this was just a pretext to play with Bun & Elysia.
I had a tweet about it mildly blow up, and it got me more curious about that combo to build backend services (I still love Node.js + Fastify 🫶).
The result so far: Bun is so fr****ing fast 🤯
Not just in req/sec (I don't particularly care in this case), but for the DX:
- Instant code reload / server restart
- Sub-second package installs
- Sub-second unit tests
- CI completes in ~10s
The unexpected side-effect of speed is that it makes agentic coding much more enjoyable.
No more having the agent stuck in a wait 5 && ls -la loop.
Elysia is really nice too, the focus on type-safety is something I want to play with a bit more, and see how it scales in terms of code organisation, community plugins, and overall DX.
This project was mostly vibe-coded 1 by GitHub Copilot + Claude Sonnet 4.5, as I don't have enough free time to spend on this side-project.
This README (from About down to here) was written by hand without tab completion.
Footnotes
-
In the sense that the LLM wrote the code, but I reviewed it and directed it with tests. Vibe-engineering would be a better term. ↩
