Lockfiles breaks semantic versioning

  • Bad: Lockfiles in packages breaks semantic versioning.
  • Good: Lockfiles in apps breaks semantic versioning.

I’ve no issue using a lockfile in apps, it’s a good thing, that’s the end of talking about apps.

I love Semantic Versioning no matter the language, but today I’m writing about npm modules and what lockfiles mean to semantic versioning for packages.

There are two common schools of thought, the first here from the prolific opensource contributor Sindre Sorhus, on his AMA he writes:

“Lockfiles for apps, but not for packages. Lockfiles are great for apps where you want a controlled reproducible environment, but for packages this doesn’t make much sense. The package-lock.json files in dependencies are ignored, so the lockfile only applies when users run npm install in the package repo. If you use a lockfile for packages, your local dependency tree will not match the dependency tree of users having your package as a dependency. This can potentially cause problems if one of your package dependencies breaks your package in a patch release. The lockfile will prevent you from seeing the problem locally, but it will affect your users.”

The counter-argument to the above is Yarn’s take on the subject, that everything should include a lockfile, it’s a bit of a read, I’ll wait here.

My retort to Yarn’s argument linked is as I stated in my opening, Lockfiles breaks semantic versioning, if you use a lockfile there is no semantic versioning and using ~ or ^ for modules in `package.json` is superfluous.

Yarn suggests that the updating of dependencies is a burden, it is, but not how Yarn sees it IMHO, we have tests that are tested in Travis CI, when not caching npm dependencies at Travis CI a fresh install of the dependencies takes place for each new pull request or commit and triggers a Travis CI build to which Travis CI installs these latest dependencies based on the semantic version range of the package in question. If there are errors, the build fails and can then be investigated further.

Doing it the Yarn way sees no automation or way of respecting semantic versioning for modules, everything becomes a manual process, either a user (“User Burden”) or a contributor (“Contributor Burden”) comes into play, either the user, who would, in fact, become a contributor has to make a conscious decision to start the manual process of checking for and updating a package’s dependencies.

Yarn’s closing summarizes that without lockfiles everything is more complicated, also suggesting there should be improved tools to make the automatic upgrading of packages painless, it makes sense right up until you try to work out where semantic versioning fits into this equation, it doesn’t, Yarn locks everything down to a specific version negating all semantic versioning.

Semantic versioning isn’t foolproof, it’s not perfect, humans make mistakes, I’ve made plenty and released a patch version moments later after noticing, if I didn’t notice myself and it is brought to my attention sometime later I release a patch version. Any other packages that are consuming my package have a hands free update waiting for them with their next CI build or deployment without the need for human intervention.

Reset the Net

The WordPress.com Blog

A year ago today, we joined the world in shock on learning that governments were spying on internet users around the world. Tapping internet service providers’ undersea cables, intentionally and secretly weakening encryption products,  surreptitiously collecting everything from call metadata to photos sent over the internet by US citizens — nothing was off limits.

Just as troubling as the revelations themselves is the fact that since last summer, little if anything has changed. Despite a lot of rhetoric, our three branches of government in the United States have not made many concrete steps toward truly protecting citizens from unchecked government surveillance.

Automattic has been a strong supporter of efforts to reform government surveillance. We’ve supported reform legislation in Congress, and participated in the Day We Fight Back, earlier this year. More importantly, we aim to make our own legal processes for securing the information our users entrust to us…

View original post 144 more words

bbPress dev chat summary for Nov 21, 2012


  • To have a chat about bbPress 2.3 goals

bbPress 2.2.2

  • #1964 Markup on user profile page doesn’t work with most themes

bbPress 2.3 Goals

counter, moderation, hierarchical forums

topics and/or Tickets Discussed

  • #1694 Add user counter functions for topics and replies
  • labels (badges) admin
  • Improved Forum Moderation see #459 for starters
  • Hierarchical Forum Layout see #1958
  • #1764 Filter page title prefixes
  • #1792 Add a Who is online widget
  • #1917 tabindex issue on new topic form
  • Forum Statistics Widget & Shortcode based on /extras/page-forum-statisics.php Template
  •  bbP beta tester plugin
  • bbPress Search see #1575

The full chat log is here.

Bookmarks for February 5th from 17:24 to 21:58

These are my links for February 5th from 17:24 to 21:58:

links for 2011-09-28