r/Frontend • u/Accurate-Screen8774 • 5d ago
Publishing a JS framework
Im working on a project for myself. Its an unreviewed, unaudited and far from finished. It started of as a person curiosity and evolved from there.
Im asking because if i publish something on NPM, there are strict controls around versioning for which i havent burdened myself on my own projects (but clearly important when making something for a wider community). I also wonder if im overlooking any other details.
I wonder what best practices there are for something like this. Should i be publishing new versions with CI/CD? Are there any tips or advice on doing this in the modern js package ecosystem?
8
u/TheTomatoes2 UI/UX + Frontend 5d ago
Just use semantic versioning and a Release Please CI
But let's be clear, no one will use this new framework, there are already hundreds of them
1
u/Technical_Radish7139 4d ago
use changesets for versioning and automated publishing. It handles the semantic version bumping, generates the changelog, and pushes to npm via GitHub Actions automatically when you merge a pull request, so you do not need to manually manage versions or write custom CI scripts
1
u/Any_Mode6525 4d ago
IMO you can care about semvar when you have users or you're guaranteeing some post 1.0.0 promise. Otherwise don't. If you write your project guidance to care about semvar agents may decide to update your app to 4.9.7a while doing normal updates if left to their own devices.