You can “weaken” package version constraints by editing your .meteor/packages file and adding an ! to the package:
coffeescript@2.4.1! # note the !
To quote the changelog:
If a package version constraint in
.meteor/packagesends with a!
character, any other (non-!) constraints on that package elsewhere in
the application will be weakened to allow any version greater than or
equal to the constraint, even if the major/minor versions do not match.For example, using both CoffeeScript 2 and
practicalmeteor:mochaused
to be impossible (or at least very difficult) because of this
api.versionsFrom("1.3")
statement, which unfortunately constrained thecoffeescriptpackage to
version 1.x. In Meteor 1.8, if you want to updatecoffeescriptto
2.x, you can relax thepracticalmeteor:mochaconstraint by puttingcoffeescript@2.2.1_1! # note the !in your
.meteor/packagesfile. Thecoffeescriptversion still needs
to be at least 1.x, so thatpracticalmeteor:mochacan count on that
minimum. However,practicalmeteor:mochawill no longer constrain the
major version ofcoffeescript, socoffeescript@2.2.1_1will work.