Closed steventebrinke closed 5 years ago
Are there any workarounds for this? I'm assuming I'm running into this problem … Upgraded to 1.6.1. and all my peerlibrary packages downgraded a few version (peerdb dropped from 0.24 to 0.20). So I've seen most peerlibrary packages got upgraded to Coffeescript 2 and so I've pinned the versions to the newest ones (in an attempt to fix my downgraded dependencies), only to run into conflicting versions:
Conflict: Constraint coffeescript@1.2.4 is not satisfied by coffeescript 2.0.3_4.
Constraints on package "coffeescript":
* coffeescript@2.0.3_3 <- peerlibrary:peerdb 0.25.0 <- peerlibrary:peerdb-migrations 0.4.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:peerdb 0.25.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:directcollection 0.7.0 <- peerlibrary:peerdb-migrations 0.4.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:directcollection 0.7.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:peerdb-migrations 0.4.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:reactive-publish 0.6.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:server-autorun 0.7.1 <- peerlibrary:reactive-mongo 0.2.2 <- peerlibrary:reactive-publish 0.6.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:server-autorun 0.7.1 <- peerlibrary:reactive-publish 0.6.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:server-autorun 0.7.1 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:fiber-utils 0.9.1 <- peerlibrary:server-autorun 0.7.1 <- peerlibrary:reactive-mongo 0.2.2 <- peerlibrary:reactive-publish 0.6.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:fiber-utils 0.9.1 <- peerlibrary:server-autorun 0.7.1 <- peerlibrary:reactive-publish 0.6.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:fiber-utils 0.9.1 <- peerlibrary:server-autorun 0.7.1 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:reactive-mongo 0.2.2 <- peerlibrary:reactive-publish 0.6.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:extend-publish 0.5.0 <- peerlibrary:reactive-publish 0.6.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@1.2.4 <- peerlibrary:blaze-components 0.22.0 <- peerlibrary:blaze-common-component 0.4.3 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@1.2.4 <- peerlibrary:blaze-components 0.22.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@1.0.5 <- peerlibrary:base-component 0.16.0 <- peerlibrary:blaze-components 0.22.0 <- peerlibrary:blaze-common-component 0.4.3 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@1.0.5 <- peerlibrary:base-component 0.16.0 <- peerlibrary:blaze-components 0.22.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:data-lookup 0.2.0 <- peerlibrary:blaze-components 0.22.0 <- peerlibrary:blaze-common-component 0.4.3 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:data-lookup 0.2.0 <- peerlibrary:blaze-components 0.22.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@1.2.3 <- peerlibrary:blaze-common-component 0.4.3 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* coffeescript@2.0.3_3 <- peerlibrary:check-extension 0.4.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
There's also a problem with babel:
error: Conflict: Constraint babel-compiler@6.8.5 is not satisfied by babel-compiler 7.0.5.
Constraints on package "babel-compiler":
* babel-compiler@~7.0.0 <- top level
* babel-compiler@7.0.0 <- ecmascript 0.10.5
* babel-compiler@7.0.0 <- standard-minifier-js 2.3.2
* babel-compiler@7.0.0 <- minifier-js 2.3.3 <- standard-minifier-js 2.3.2
* babel-compiler@6.19.4||7.0.0 <- coffeescript-compiler 2.0.3_4 <- coffeescript 2.0.3_4 <- peerlibrary:base-component 0.16.0 <- peerlibrary:blaze-components 0.22.0 <- peerlibrary:blaze-common-component 0.4.3 <-
retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* babel-compiler@6.19.4||7.0.0 <- coffeescript-compiler 2.0.3_4 <- coffeescript 2.0.3_4 <- peerlibrary:base-component 0.16.0 <- peerlibrary:blaze-components 0.22.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* babel-compiler@6.19.4||7.0.0 <- coffeescript-compiler 2.0.3_4 <- coffeescript 2.0.3_4 <- peerlibrary:blaze-common-component 0.4.3 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* babel-compiler@6.19.4||7.0.0 <- coffeescript-compiler 2.0.3_4 <- coffeescript 2.0.3_4 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* babel-compiler@6.8.5 <- peerlibrary:ecmascript-compiler 0.5.7_2 <- peerlibrary:util 0.5.0 <- peerlibrary:peerdb 0.25.0 <- peerlibrary:peerdb-migrations 0.4.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
* babel-compiler@6.8.5 <- peerlibrary:ecmascript-compiler 0.5.7_2 <- peerlibrary:util 0.5.0 <- peerlibrary:peerdb 0.25.0 <- retronator:artificialengines 1.0.0 <- retronator:app 0.28.0
Any solutions, or is it just downgrade back to Meteor 1.6.0? Or I guess, better asked, what would it require to fix the package? Something substantial or just increase package versions?
For now, I'm just sticking with Meteor 1.6.0. I've not tested what would be required to fix this package, it might be just increasing package versions, but that has to be tested.
Pinging @mitar to see if there's any hope left now that he's using Vue. 😁
Yea, I have this on my radar. I have many packages in CoffeeScript and this is on top of the tree, I had first to port all other packages.
@steventebrinke @MatejJan In the meantime, as a workaround, you can clone my forks into your packages directory:
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)
Upgrading to 1.6.1 really is a nightmare
@mitar any chance of making peerlibrary compatible with Meteor 1.6.1+? Its a shame for all those projects out there still depending on it.
Published a version for CoffeeScript2 as peerlibrary:blaze-components@0.23.0
. Sorry that it took so long.
Meteor 1.6.1 ships with an updated Babel compile, which means that the coffeescript package must be updated to version 2, whereas blaze-components depends on coffeescript 1. Would it be possible to also support coffeescript 2?