Is the intent to encourage developers to defer releasing until a stable version is reached ?

Write your answer…

4 answers

That is a good question.

NPM follows the semver conventions and as such it encourages you to ship code starting at v1.0.0. Unfortunately, some projects ignore that rule and can cause troubles when calculating version numbers used for dependency management or publishing to npmjs.org.

1 Beer1
Spot On1

Hashnode is building a friendly and inclusive dev community. Come jump on the bandwagon!

  • 💬 A beginner friendly place

  • 🧠 Stay in the loop and grow your knowledge

  • 🍕 >500K developers share programming wisdom here

  • ❤️ Support the growing dev community!

Register ( 500k+ developers strong 👊)

If I setup a new development environment one thing I do is changing the npm init defaults.

npm config edit --global

I set init-author-name, init-author-email and init-version. A new initialized project is never "stable". So my default version is 0.1.0.

To me 1.0.0 is a stable version...

NPM specifies that it uses/expects SemVer so you're absolutely right.

Reply to this…

Personally I think init should start at 0.1.0, being the first dev version. The author should choose when to cut 1.0.0 and set their API.