The registry gateway

Your computer first asks Scopeferry where a package is registered. Scopeferry returns a redirect to your computer, which then requests the package directly from npm, JSR, or a self-hosted registry, without passing through Scopeferry. Illustrative routes: lodash goes to registry.npmjs.org by default, @acme/ui matches a scope mapped to npm.jsr.io, and @acme/core has a package override pointing to registry.acme.com. These are examples, not live traffic.$Self-hosted

What?

Before Scopeferry, when you ran npm install <package>, your package manager (npm, bun, yarn, pnpm, etc.) went to registry.npmjs.org to fetch that package.

With Scopeferry, your package manager first goes to gateway.scopeferry.com to find where that package is registered. Scopeferry then redirects that request to whichever registry that package lives in.

Why?

Prior to Scopeferry, consumers had to configure a specific rule to install packages hosted outside npm, such as on a self-hosted registry. They had to repeat this setup for every package whose author chose an alternative registry.

This split architecture allows for much greater flexibility and freedom for package authors, whilst keeping the simple ergonomics of npm install <package> for consumers.

How?

Scopeferry is where package authors define where that redirect should go. Simply claim a ‘scope’, such as your organisation’s name (like @effect, @tanstack, etc.), or a top-level package like lodash, react, ai, etc., and then choose the registry that scope should redirect to.

If a scope has not been claimed, it falls back to registry.npmjs.org.

Consumers of packages set their registry to gateway.scopeferry.com. This single change maintains complete backward compatibility with npm. For consumers already using Scopeferry, no changes are needed for any future packages that move away from npm.

Motivation

Scopeferry was born from the desire to offer more flexibility and choice in the npm ecosystem. Whilst npm has enabled a rich ecosystem to thrive, we believe it is important to give package authors the freedom to own the complete lifecycle of publishing their work.

Today, we exist in a complex dynamic where authors depend on this ecosystem to make a living. And yet, authors are forced to settle for a single place of distribution for all of their work. Can you imagine only having a single place to host other software like a web app or a game server?

Whilst alternatives to npm do exist, the experience of using packages whose authors chose an alternative route has always been inferior to the default experience. We want to change that.

Right now, Scopeferry is a gateway. This is the first step in building a more distributed ecosystem. Further down the line, we will offer our own registry SDK for making self-hosting quick and easy.

We will also offer our own registry for those who do not want to self-host but want a better publishing experience than npm offers.