Compatibility with Meteor 1.6.1, Babel 7 and Coffeescript 2

[jankapunkt]

Updating to Meteor 1.6.1 creates an implicit dependency to coffeescript2

Is there a goal / effort to update this package (related: #91 ) ?

[theodorDiaconu]

@jankapunkt try using cultofcoders:mocha

[jankapunkt]

The package cultofcoders:mocha is not open, there is no source to view. The referenced github repository is instead this one. I don't include closed packages in my project.

I'd prefer the author team to accept #91 or give hints to improvement.

meteortesting:mocha is also not an option, since it has a totally different reporting behavior and also breaks my CI pipeline.

Edit: okay I found the source here on gh. They just forhot to correct the github link on their atmosphere package. But even then - is there no option, that this repo is merging their version?

[theodorDiaconu]

@jankapunkt I just published it directly for my use. When I get some time I will make source public.

[aogaili]

The cult of coders package is published here now. Ideally the maintainers of this repo update and push to atmosphere, it doesn't seem that hard to make it work again and it's less then ideal to end with two forks and packages on Atmosphere.

[serut]

Hello @theodorDiaconu, I'm the author of meteor-coverage, and my package also use practicalmeteor dependencies. I would like to know if that's possible to publish a fork of mocha-console-runner on the cultofcoders name. Indeed, this line must be edited to allow us to run tests on CI platforms.

[theodorDiaconu]

@serut yes ofcourse, no problem!

[serut]

Nice ! Thank you.
I've updated the readme of my package in that way : https://github.com/serut/meteor-coverage#specific-setup-for-meteor-apps

[fumbleforce]

@theodorDiaconu Is your fork supposed to make it work with coffeescript 2, or just to avoid the implicit inclusion of cs2 and add support for 1.6.1?

[theodorDiaconu]

@JorgeER works with coffeescript 2.

[fumbleforce]

@theodorDiaconu thanks for replying so quickly! My problem is that it seems the package drags in other practicalmeteor packages like practicalmeteor:chai and sinon, which brings along coffescript conflicts, as they depend on coffeescript 1 it looks like. How did you get around that?

[theodorDiaconu]

@JorgeER go npm! use chai and sinon from there.

[fumbleforce]

@theodorDiaconu Sure, but it seems like the mocha still pulls in the old packages (which I dont use) in package.js, which again depend on cs1:

In cultofcoders:mocha:

api.use([
    'practicalmeteor:mocha-core@1.0.1',
    'practicalmeteor:loglevel@1.2.0_2',
    'practicalmeteor:chai@2.1.0_1',
    'practicalmeteor:sinon@1.14.1_2',
  ]);

  api.imply([
    'practicalmeteor:mocha-core@1.0.1',
    'practicalmeteor:loglevel@1.2.0_2',
    'practicalmeteor:chai@2.1.0_1',
    'practicalmeteor:sinon@1.14.1_2',
  ]);

and Im getting

error: Conflict: Constraint coffeescript@2.0.3_3 is not satisfied by coffeescript 1.0.17.
Constraints on package "coffeescript": 
* coffeescript@2.0.3_3 <- simonsimcity:job-collection 1.6.1
* coffeescript@1.0.3 <- practicalmeteor:sinon 1.14.1_2 <- cultofcoders:mocha 2.4.6 
* coffeescript@1.0.3 <- practicalmeteor:chai 2.1.0_1 <- cultofcoders:mocha 2.4.6 
* coffeescript@1.0.3 <- practicalmeteor:loglevel 1.2.0_2 <- cultofcoders:mocha 2.4.6
* coffeescript@1.0.15 <- cultofcoders:mocha 2.4.6