Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Top-level dependency conflict when moving to Meteor 1.6.1

See original GitHub issue

We’ve been taking apart our app trying to upgrade to Meteor 1.6.1 and have run into issues specific to Coffeescript 1.x. We’ve successfully untangled all of the Peerlibrary packages that were still using Coffeescript 1 and are now on Coffeescript 2 as a top-level dependency throughout.

Unfortunately, when i try to add easy:search back to the app, I run into version constraint issues since easy:search depends on peerlibrary:server-autorun@0.5.2 + peerlibrary:reactive-publish@0.4.0 and we’re on peerlibrary:server-autorun@0.7.1 + peerlibrary:reactive-publish@0.6.0.

See output below:

While selecting package versions:
error: Potentially incompatible change required to top-level dependency:
peerlibrary:reactive-publish 0.4.0, was 0.6.0.
Constraints on package "peerlibrary:reactive-publish":

Potentially incompatible change required to top-level dependency:
peerlibrary:server-autorun 0.5.2, was 0.7.1.
Constraints on package "peerlibrary:server-autorun":
* peerlibrary:server-autorun@0.5.2 <- peerlibrary:reactive-publish 0.4.0
* peerlibrary:server-autorun@0.5.1 <- peerlibrary:reactive-mongo 0.1.1 <-
peerlibrary:reactive-publish 0.4.0

I’m pretty certain this is the last thing holding us back from our update to Meteor 1.6.1 - would you be able to do a new release with a bump to peerlibrary:server-autorun@0.7.1 and peerlibrary:reactive-publish@0.6.0?

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

mitarcommented, Sep 23, 2019

Published a version for CoffeeScript2 as peerlibrary:blaze-components@0.23.0. Sorry that it took so long.

0reactions

maxficommented, Jun 18, 2018

As a temporary workaround, until meteor-blaze-components and meteor-base-component are officially updated you can clone my forks of those dependencies:

cd packages

git clone git@github.com:maxfi/meteor-blaze-components.git
(cd meteor-blaze-components && git checkout ca6d1d4334d915bd855963b9b1dee0022be0f3e5)

git clone git@github.com:maxfi/meteor-base-component.git
(cd meteor-base-component && git checkout e0bf4850b7f3bf1eb989a38e83be76ee5a85ad73)

– https://github.com/peerlibrary/meteor-blaze-components/issues/152#issuecomment-398028333