Error on Meteor Update 1.6.1 when using practicalmeteor:mocha

[peerlibrary]

Error on Meteor Update 1.6.1 when using practicalmeteor:mocha

[mitar]

Accounts package moved to NPM: https://github.com/softwarerero/meteor-accounts-t9n#version-230

[mitar]

That's a bug in your app. This package is not using ReactiveVar.

[mitar]

(It uses it only in tests. And dependency is defined here.)

[nonfungibletunji]

So Uses when running test on the package??? S Tunji Turner sightuary @sightuary

…

On Feb 25, 2018, at 7:18 AM, Mitar ***@***.***> wrote: (It uses it only in tests.) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[mitar]

But the dependency is defined in package.js.

[nonfungibletunji]

Yeah but the package is setup for version 1.4+, I am running into the error using version meteor 1.6.1 S Tunji Turner sightuary @sightuary

…

On Feb 25, 2018, at 7:28 AM, Mitar ***@***.***> wrote: But the dependency is defined in package.js. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[mitar]

Just packages versions uses from 1.4

Anyway, I cannot reproduce your issue. I ran this on Meteor 1.6.1 and tests work for me.

[mitar]

So please create a small reproduction.

[nonfungibletunji]

Will do thanks S Tunji Turner sightuary @sightuary

…

On Feb 25, 2018, at 7:40 AM, Mitar ***@***.***> wrote: So please create a small reproduction. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[nonfungibletunji]

I just removed the package, the app is a migration from 1.2 to 1.6.1. S Tunji Turner sightuary @sightuary

…

On Feb 25, 2018, at 7:40 AM, Mitar ***@***.***> wrote: So please create a small reproduction. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[mitar]

OK, but can you make a small app where this is failing like you are describing?

[nonfungibletunji]

Yes I can S Tunji Turner sightuary @sightuary

…

On Feb 25, 2018, at 11:24 AM, Mitar ***@***.***> wrote: OK, but can you make a small app where this is failing like you are describing? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[atomoc]

I have the same!

[atomoc]

And on command meteor update --all-packages:

This project is already at Meteor 1.6.1, the latest release.
=> Errors while upgrading packages:           
                                              
While selecting package versions:
error: Conflict: Constraint [email protected] is not satisfied by coffeescript 2.2.1_1.
Constraints on package "coffeescript":
* [email protected] <- zimme:collection-timestampable 1.0.9
* [email protected] <- zimme:collection-behaviours 1.1.3 <- zimme:collection-timestampable 1.0.9
* [email protected]_3 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_3 <- peerlibrary:server-autorun 0.7.1 <- peerlibrary:reactive-mongo 0.2.2 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_3 <- peerlibrary:server-autorun 0.7.1 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_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
* [email protected]_3 <- peerlibrary:fiber-utils 0.9.1 <- peerlibrary:server-autorun 0.7.1 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_3 <- peerlibrary:reactive-mongo 0.2.2 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_3 <- peerlibrary:extend-publish 0.5.0 <- peerlibrary:reactive-publish 0.6.0

[atomoc]

And:

$ meteor add peerlibrary:[email protected]
 => Errors while adding packages:             
                                              
While selecting package versions:
error: Conflict: Constraint [email protected] is not satisfied by coffeescript 2.0.3_4.
Constraints on package "coffeescript":
* [email protected] <- zimme:collection-timestampable 1.0.9
* [email protected] <- zimme:collection-behaviours 1.1.3 <- zimme:collection-timestampable 1.0.9
* [email protected]_3 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_3 <- peerlibrary:server-autorun 0.7.1 <- peerlibrary:reactive-mongo 0.2.2 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_3 <- peerlibrary:server-autorun 0.7.1 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_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
* [email protected]_3 <- peerlibrary:fiber-utils 0.9.1 <- peerlibrary:server-autorun 0.7.1 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_3 <- peerlibrary:reactive-mongo 0.2.2 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_3 <- peerlibrary:extend-publish 0.5.0 <- peerlibrary:reactive-publish 0.6.0

[atomoc]

It is necessary to refrain while from using.

[mitar]

So nobody willing to create a reproduction?

[mitar]

Because things work for me:

$ meteor create test-app
Created a new Meteor app in 'test-app'.       

To run your new app:                          
  cd test-app                                 
  meteor                                      
                                              
If you are new to Meteor, try some of the learning resources here:
  https://www.meteor.com/tutorials            
                                              
meteor create --bare to create an empty app.  
meteor create --full to create a scaffolded app.
                                              
$ cd test-app/
$ meteor add peerlibrary:reactive-publish
                                              
Changes to your project's package version selections:
                                              
coffeescript                  added, version 2.0.3_4
coffeescript-compiler         added, version 2.0.3_4
peerlibrary:assert            added, version 0.2.5
peerlibrary:extend-publish    added, version 0.5.0
peerlibrary:fiber-utils       added, version 0.9.1
peerlibrary:reactive-mongo    added, version 0.2.2
peerlibrary:reactive-publish  added, version 0.6.0
peerlibrary:server-autorun    added, version 0.7.1

                                              
peerlibrary:reactive-publish: Reactive publish endpoints
$ meteor           
[[[[[ .../test-app ]]]]]                   

=> Started proxy.                             
=> Started MongoDB.                           
=> Started your app.                          

=> App running at: http://localhost:3000/

[atomoc]

Version of the meteor what?

[mitar]

@atomoc, I do not understand your question.

[atomoc]

Meteor v.1.6.1 ?

[mitar]

Yes, this is what I just ran, which uses Meteor 1.6.1 by default. Please try to create a small reproduction yourself and put a repo on GitHub.

[atomoc]

On a clean project with the same package.json and .meteor/packages files everything is ok, until I can understand what the problem is.

[nonfungibletunji]

Again my test app deployed as well , with the dependency S Tunji Turner sightuary @sightuary

…

On Feb 27, 2018, at 7:11 AM, Сергей Савельев ***@***.***> wrote: On a clean project with the same package.json and .meteor/packages files everything is ok, until I can understand what the problem is. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[mitar]

@stunjiturner, so does it work for you or no? I do not understand.

[nonfungibletunji]

It does not work for the existing app, only for a newly created meteor 1.6.1 test app. S Tunji Turner sightuary @sightuary

…

On Feb 27, 2018, at 12:15 PM, Mitar ***@***.***> wrote: @stunjiturner, so does it work for you or no? I do not understand. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[mitar]

OK. So please find what is the difference and make a reproduction. It works for me, so I cannot really help until we can at least have a small example.

[atomoc]

I tried to use ReactiveVar yesterday, but I got errors. Clearly something is not so simple with him.

[atomoc]

@mitar Here need a large reproduction most likely

[atomoc]

I think the problem is in Cordova

[janat08]

https://github.com/janat08/blockrazor/tree/reactivePublications
isn't small.

[brendonboshell]

This issue seems to happen when other conflicting packages have been installed, perhaps due to the way Meteor resolves conflicting dependencies? For example, having both 'practicalmeteor:mocha' and 'peerlibrary:reactive-publish' packages will result in this error.

To replicate:

1. meteor create simple-todos --release 1.6.1
2. cd simple-todos
3. meteor add practicalmeteor:mocha
4. meteor add peerlibrary:reactive-publish
5. meteor --inspect-brk

It seems the tests.coffee.js file is included, which results in the ReactiveVar is not defined error.

Meteor decides to install 0.4.0:

$ meteor list
autopublish                   1.0.7  (For prototyping only) Publish the entire database to all clients
blaze-html-templates          1.1.2  Compile HTML templates into reactive UI with Meteor Blaze
ecmascript                    0.10.5  Compiler plugin that supports ES2015+ in all .js files
es5-shim                      4.7.3  Shims and polyfills to improve ECMAScript 5 support
insecure                      1.0.7  (For prototyping only) Allow all database writes from the client
meteor-base                   1.3.0  Packages that every Meteor app needs
mobile-experience             1.0.5  Packages for a great mobile user experience
mongo                         1.4.5  Adaptor for using MongoDB and Minimongo over DDP
peerlibrary:reactive-publish  0.4.0* Reactive publish endpoints
practicalmeteor:mocha         2.4.5_6  Write package tests with mocha and run them in the browser or from the command line with spacejam.
reactive-var                  1.0.11  Reactive variable
shell-server                  0.3.1  Server-side component of the `meteor shell` command.
standard-minifier-css         1.4.1  Standard css minifier used with Meteor apps by default.
standard-minifier-js          2.3.2  Standard javascript minifiers used with Meteor apps by default.
tracker                       1.1.3  Dependency tracker to allow reactive callbacks

Running meteor add peerlibrary:[email protected] results in:

 => Errors while adding packages:             
                                              
While selecting package versions:
error: Conflict: Constraint [email protected] is not satisfied by coffeescript 2.0.3_4.
Constraints on package "coffeescript":
* [email protected] <- practicalmeteor:mocha 2.0.1-rc0
* [email protected]_3 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_3 <- peerlibrary:server-autorun 0.7.1 <- peerlibrary:reactive-mongo 0.2.2 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_3 <- peerlibrary:server-autorun 0.7.1 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_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
* [email protected]_3 <- peerlibrary:fiber-utils 0.9.1 <- peerlibrary:server-autorun 0.7.1 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_3 <- peerlibrary:reactive-mongo 0.2.2 <- peerlibrary:reactive-publish 0.6.0
* [email protected]_3 <- peerlibrary:extend-publish 0.5.0 <- peerlibrary:reactive-publish 0.6.0

Conflict: Constraint spacejamio:[email protected]_2 is not satisfied by spacejamio:chai 1.0.0.
Constraints on package "spacejamio:chai":
* spacejamio:[email protected]_2 <- practicalmeteor:mocha 2.0.1-rc0

[knirirr]

I'm seeing the same issue as @brendonboshell and can reproduce the same crash with the simple-todos as mentioned above. What I can't manage at the moment is to get node-inspector installed, apparently due to this issue: node-inspector/v8-debug#41

[knirirr]

If anyone has had any luck in finding a solution to this I'd be very interested to hear it.

Meanwhile, I note that an older version of my application using Meteor 1.6-beta.26 does not show this problem, so it does indeed seem to be related to 1.6.1.

[mitar]

I am using this package with 1.6.1.1 without any problems. I think the issue is in practicalmeteor:mocha which is forcing an old CoffeeScript version. It should be updated to CoffeeScript 2.

I am using meteortesting:mocha which works well.

[mitar]

Not sure why it is not picking 0.5.0 though for you. That version of this package uses CoffeeScript 1 and works well.

[mitar]

See issue here: practicalmeteor/meteor-mocha#99

[mitar]

And: practicalmeteor/meteor-mocha#91

[mitar]

So can somebody try meteor add peerlibrary:[email protected] and report what happens?

[mitar]

Ah, you get:

While selecting package versions:
error: Conflict: Constraint [email protected] is not satisfied by babel-compiler 7.0.8.
Constraints on package "babel-compiler":
* babel-compiler@~7.0.6 <- top level
* [email protected] <- ecmascript 0.10.8
* [email protected] <- minifier-js 2.3.4 <- standard-minifier-js 2.3.3
* [email protected] <- standard-minifier-js 2.3.3
* [email protected] <- coffeescript 1.11.1_3 <- peerlibrary:extend-publish 0.4.0 <- peerlibrary:reactive-publish 0.5.0
* [email protected] <- coffeescript 1.11.1_3 <- peerlibrary:reactive-publish 0.5.0

[mitar]

So not sure how to fix this. It is really a problem of practicalmeteor:mocha for not being updated to 1.6.1.

[knirirr]

Thanks for your further comments.
I've removed practicalmeteor:mocha and replaced it with meteortesting:mocha. Unfortunately, this issue persists.

Edit: The list of packages I'm using is at https://bitbucket.org/knirirr/beecount3/src/4652c46442fee9443c69be0722c485babd19c0ba/.meteor/packages?at=master&fileviewer=file-view-default

[mitar]

You have now update all packages with meteor update --all-packages.

[mitar]

I still see practicalmeteor:mocha in your list of packages.

[knirirr]

I've not checked in the changes I made locally, and don't plan to do so until I can get the application working again, so it still shows the old package. In addition to the package removal/addition previously mentioned I've also run meteor update --all-packages, and the problem persists. This procedure should therefore reproduce the problem.

1. Clone https://bitbucket.org/knirirr/beecount3.git
2. meteor remove practicalmeteor:mocha
3. meteor add meteortesting:mocha
4. meteor update --all-packages
5. meteor

[mitar]

Yea, you have other dependencies on old CoffeeScript. You should really complain to Meteor about all this situation. They managed to break many libraries using CoffeeScript and many of them are not maintained really anymore.

So try:

1. Clone https://bitbucket.org/knirirr/beecount3.git
2. meteor update
3. meteor update --all-packages
4. meteor add [email protected]_1

And you will see all conflicts.

* [email protected] <- zimme:active-route 2.3.2
* [email protected] <- softwarerero:accounts-t9n 1.3.11 <- useraccounts:core 1.14.2 <- useraccounts:flow-routing 1.14.2
* [email protected] <- practicalmeteor:mocha 2.4.5_6
* [email protected] <- practicalmeteor:loglevel 1.2.0_2 <- practicalmeteor:mocha 2.4.5_6
* [email protected] <- practicalmeteor:chai 2.1.0_1 <- practicalmeteor:loglevel 1.2.0_2 <- practicalmeteor:mocha 2.4.5_6
* [email protected] <- practicalmeteor:chai 2.1.0_1 <- practicalmeteor:mocha 2.4.5_6
* [email protected] <- practicalmeteor:sinon 1.14.1_2

So besides practicalmeteor:mocha you have some other as well.

So there is not really much one can do here. Meteor broke that old already published packages do not work by forcing downgrade to broken versions. While new fixed packages require also other packages to be upgraded. And many are not maintained anymore.

[knirirr]

Thanks for looking into it - I'll see about pursing the issue elsewhere in case I get any luck.
The testing packages I could probably dispense with (I need to re-work all my tests anyway) but the accounts stuff is essential.

[mitar]

I am using this in my own apps with Meteor 1.6.1 and meteortesting:mocha and I do not see any issues. So closing this now.