https://kizi.to/tags/npm/ Recent content in npm on Kizito Hugo en-us Sat, 29 Aug 2026 00:00:00 +0000 https://kizi.to/prod-like-a-pro-npm/ Sat, 29 Aug 2026 00:00:00 +0000 https://kizi.to/prod-like-a-pro-npm/ <p>similar to how i&rsquo;ve been able to automate <a href="https://kizi.to/prod-like-a-pro/">how i deploy backend services</a>, i wanted to ensure that when releasing libraries, every step of the way was fully automated.</p> <p>overall, i wanted the following to hold true:</p> <ol> <li>i work on new changes on the library in a feature branch.</li> <li>when i raise a pull request from the feature branch to main, a “preview” version of the changes which i just worked on gets published to npm (or whichever registry) - something installable by anyone.</li> <li>once validated and merged, a “canary” or “next” version gets automatically released to the registry.</li> <li>once i am ready to “cut” a new version, i create a new release &amp; tag on github, then publishing it properly releases the library in the registry on the <code>latest</code> tag.</li> </ol> <p>after trialing out the above for a bit, it became clear that there was no value in having step 2 since i work solo on the library.</p>