· javascript

No, npm, “estee” is not a typo of “testem”

So, alright, look, here's the thing.


Storyteller has a really long npm namespace because “storyteller” is a really common word, and so “@storyteller/” was already taken (by someone who doesn’t actually seem to use it, which, if you’re reading this, I’m still interested in your namespace!). So we’re stuck with “@storyteller-platform/”, and that means our command line tool for book forced alignment is named “@storyteller-platform/align”, and so you need to run “npx @storyteller-platform/align --help”, etc, which is a handful!

And so we came up with a cute nickname, “estee” (get it? Storyteller -> ST -> estee?), and we were pretty happy with it, so I went to publish a v0.0.1 to npm so I could set up Trusted Publishing with our GitLab repo and then this happened: 403 Forbidden - PUT https://registry.npmjs.org/estee - Package name too similar to existing packages espree,testem ...

I mean I can almost understand “espree”. I don’t actually see how someone could accidentally typo “espree” as “estee”, but at least they're similarly shaped.

Earlier coverage

Related coverage

Also worth reading

  1. Angular 20.3.35 and 21.2.26 released, fixing downgraded component template compilation
  2. next.js 16.4.4 released
  3. next.js 16.5.0-canary.35 released with error handling fixes, cache fixes, and docs clarifications
  4. dbreunig/nesformer
  5. Defending the patch gap against automated attackers