If I understand things correctly: if I specify the
sacha:foo package in my
.meteor/packages file and the run
meteor update, it will use the latest version of the package it finds on Atmosphere.
If I specify
sacha:firstname.lastname@example.org, it will use
0.3.0, etc., but not
But (again, please correct me if I got it wrong) if
sacha:foo itself depends on
meteor update will not update
sacha:bar, even if
sacha:email@example.com is available on Atmosphere.
The only way to get
sacha:bar to update is to manually change it inside
This can be a problem when publishing multiple packages that depend on each other (such as @slpendido’s useraccounts). It means that if you publish a new version of a dependency package, you also have to publish a new version of the packages that depend on it, otherwise the dependency won’t get updated.
So my question is: is there any way to force Meteor to update all packages – including dependencies – to the latest version?
Or alternatively, is there a way to specify a dependency on a package without pinning it down to a version? i.e. just write
api.use("sacha:bar") instead of
api.use("sacha:firstname.lastname@example.org"), and just let Meteor use the latest version available?