Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Top-level dependency conflict when moving to Meteor 1.6.1 #637

Open
etyp opened this issue Mar 20, 2018 · 5 comments
Open

Top-level dependency conflict when moving to Meteor 1.6.1 #637

etyp opened this issue Mar 20, 2018 · 5 comments

Comments

@etyp
Copy link

etyp commented Mar 20, 2018

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?

@etyp
Copy link
Author

etyp commented Mar 21, 2018

As a temporary workaround, I've just limited us to use easysearch:core and not used the components package (using different ui).

@matteodem
Copy link
Owner

I'm quite busy as of now, but feel free to create a PR that bumps the version

@maxfi
Copy link

maxfi commented Jun 15, 2018

@matteodem I've got the same issue. Happy to help out with a PR. Just need some guidance on how to proceed. Thanks.

@maxfi
Copy link

maxfi commented 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)

-- peerlibrary/meteor-blaze-components#152 (comment)

@mitar
Copy link
Contributor

mitar commented Sep 23, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants