Yeah the upgrade to coffeescript 2 around that time caused this issue for a lot of people. Here, your babel-compiler issue is through coffeescript as a secondary dependency.
The first thing to try is to update with --allow-incompatible-update
and --all-packages
to see if it can resolve the version constraints with new versions (warning, this can introduce breaking changes to packages)
Otherwise, this is exactly the reason that in Meteor 1.8, a feature was introduced that is basically the !important
of package versioning.
So in your .meteor/packages
, you can add an !
to the end of a package to say, I want this version and please ignore version constraints from packages:
So in your case, I would try to target that coffeescript dependency with:
coffeescript@2.0.0!
More info from History.md:
The .meteor/packages
file supports a new syntax for overriding problematic version constraints from packages you do not control.
If a package version constraint in .meteor/packages
ends 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:mocha
used to be impossible (or at least very difficult) because of this api.versionsFrom("1.3")
statement, which unfortunately constrained the coffeescript
package to version 1.x. In Meteor 1.8, if you want to update coffeescript
to 2.x, you can relax the practicalmeteor:mocha
constraint by putting
coffeescript@2.2.1_1! # note the !
in your .meteor/packages
file. The coffeescript
version still needs to be at least 1.x, so that practicalmeteor:mocha
can count on that minimum. However, practicalmeteor:mocha
will no longer constrain the major version of coffeescript
, so coffeescript@2.2.1_1
will work.
PS: Welcome to the forums!