Hex retire

Mike Hoffert
Sep 7, 2018 · 2 min read

The hex retire command should help us realize that we should retire npm.

I’m at elixir conf, watching a talk by Todd Resudek. He mentioned how the hex team setup their package manager with developers in mind. Anybody that has developed packages for distribution on npm knows what I mean. Deploying patches is a pain. The package lock issues. Naming collisions. The package deprication notices aren’t apparent unless you open the readme. Kent C Dodds just tweeted about that.

So how does Hex handle these issues?

Keep the story going. Sign up for an extra free read.

You've completed your member preview for this month, but when you sign up for a free Medium account, you get one more story.
Already have an account? Sign in

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade