Trying to pin a package. What I’ve tried so far is to put the version number in my .meteor/packages
file like so:
sacha:juice@0.1.1
But unfortunately when I run meteor update
it still upgrades that package to 0.1.2 which is not what I want.
How can I pin it so that meteor update will update other packages but not this one ?
Is this (from the meteor add package
documentation) what you are looking for?
Running meteor add package@1.1.0 will add the package at version 1.1.0 or higher (but not 2.0.0 or higher). If you want to use version 1.1.0 exactly, use meteor add package@=1.1.0. You can also ‘or’ constraints together: for example, meteor add ‘package@=1.0.0 || =2.0.1’ means either 1.0.0 (exactly) or 2.0.1 (exactly).
1 Like
Doesn’t seem to work for me.
$ meteor add sacha:juice@0.1.1
Currently using sacha:juice without any version constraint.
The version constraint will be changed to 0.1.1.
sacha:juice: Juice wrapper package
$ meteor update
This project is already at Meteor 1.0.3.2, the latest release.
Changes to your project's package version selections from updating package versions:
sacha:juice upgraded from 0.1.1 to 0.1.2
I just checked and it seems like meteor add does what I was doing manually, that is adding the version spec in .meteor/packages
Neither way is working. Am I missing something?