I built a package manager because npm doesn't work in my country.

Yusup Atahanov — Sat, 03 Oct 2026 09:05:27 +0000

hi guys, my name is Yusup.

I'm a developer from Turkmenistan. If you haven't heard much about it — the internet here is one of the most locked-down in the world. npm gets blocked, connections die halfway, and some days npm install just sits there forever.

For a long time I thought that was just how it is. You wait. You retry. You keep a VPN open and hope. Setting up a React project could eat an afternoon.

At some point I got tired of being stuck, so I started building my own package manager. I called it jet. Took about 6 months, mostly at night, on my own.

The idea is simple — it should keep working when the network doesn't:

if a mirror is blocked, it quietly switches to another one mid-install
if a package is already on disk, it never touches the network
if a download dies at 80%, it continues from there instead of starting over
one small binary, no Node needed

It's not the fastest out there — bun wins that race, and I'm fine with it. I wasn't chasing a benchmark. I just wanted the thing to not fail.

A few people have tried it already. One was on a Mac — and that one got me, because I'm on Windows and never even tested there. A real stranger, somewhere out there, running something I built alone in a country where the internet fights you.

It's free, works on Windows/Mac/Linux. If your connection is rough — or censored — it might save you some pain. jet.kim

If you try it, I'd honestly love to hear what breaks. It's the first thing I've ever put out into the world.Thank you for read this post

DEV Community: Yusup Atahanov

I built a package manager because npm doesn't work in my country.