The Burden of Releasing a V1 Module

There's a reluctance and even some recommendations to never release a V1 module. Too many folks are now only releasing V0 and their continued bump versions there because they don't want to run under the risk of needing to make a small change as a breaking change per semver. A one line change might require a consumer to update 30 files if they import that package across 30 files, even if only one file needs to be changed. And so the cost of migrating that code base to the new version is not linear to the actual change itself. There's a heavier burden often on the consumers to adopt that new version.

Play episode from 16:44

Transcript

Episode notes

The AI-powered Podcast Player

Save insights by tapping your headphones, chat with episodes, discover the best highlights - and more!

Get the app