I saw on Meteor News this morning that Meteor 1.2 is released. So I entered in my console “meteor update”; after much churning, the laborious updates came to an end. I then did a “meteor list” and was informed that my meteor-base version is 1.0.1. Am I missing something (no pun intended)?
meteor-base is a new package, sort of a replacement for the meteor-platform package with much less dependencies.
It makes it easier to remove mongo or blaze for example without having to re-add in the rest of meteor
EDIT: seems it provides exports to other core packages that may need to integrate with each other - https://github.com/meteor/meteor/blob/master/packages/meteor-base/package.js
So meteor-base 1.0.1 is Meteor 1.2?
Say it ain’t so; that would be no better than much of Microsoft’s confusing numbering nomenclature.
meteor --version will give you the version of meteor, rather than the version of a package within meteor.
yeah… meteor-platform didn’t represent the release version either =P
Discussion: https://github.com/meteor/meteor/pull/4851
Yeah, that gives me 1.2.0.1
It still seems to that meteor-base and the version number should be the same, though.
As far as I understand it, Meteor version number can change even if there are no changes in meteor-base package. Why should meteor-base package number be changed then?
That makes no sense to me - if the base packages don’t change, why would the overall version number increase? That’s like being born in 1968 and saying you’re 37 years old.
The point is, Meteor is more than this one package. F.e. Meteor 1.1.0.3 (the latest 1.1 version) did only a simple change in accounts package. It didn’t touch meteor-platform package at all. So Meteor changed version to 1.1.0.3, but does it mean that meteor-platform should change its version if the package wasn’t touched?