We moved our SDK off public npm onto a private registry we host.
Our customers mainly use Donobu's SDK to run their end-to-end tests in CI/CD, with AI self-healing and triage. It was unlicensed but on public npm on purpose, so `npm i` just worked.
NPM registry has had a rough year. When we looked at alternatives, we realized self-hosting packages is not that hard anymore. Our customers continue using `npm i`. They just add a .npmrc pointing at our registry; reusing their existing Donobu API key for auth was a nice bonus.
1 comment of 4
[ 3.1 ms ] story [ 16.0 ms ] threadOur customers mainly use Donobu's SDK to run their end-to-end tests in CI/CD, with AI self-healing and triage. It was unlicensed but on public npm on purpose, so `npm i` just worked.
NPM registry has had a rough year. When we looked at alternatives, we realized self-hosting packages is not that hard anymore. Our customers continue using `npm i`. They just add a .npmrc pointing at our registry; reusing their existing Donobu API key for auth was a nice bonus.
.npmrc was the only thing needed: