Vaughn Iverson

Hi, in general this is a synchronization problem. That is, you have multiple concurrent processes potentially competing for an exclusive resource (in this case, the "right" to access an API...

Corrected "cargo" to be "payload" in the above.

@cormip What's the issue? I'm not seeing any text in your description.

Can you successfully install version 1.4.0?

Hmmm, okay, I'll try to reproduce this today. Thanks for reporting!

Hi, I'm not able to reproduce this issue. Here's what I tried. I have a simple "empty" Meteor app project here: https://github.com/vsivsi/emptyMeteorProj ```sh git clone https://github.com/vsivsi/emptyMeteorProj.git emptyProj # Cloning into...

Hmm, must be a Windows dependency of some kind. I only develop on MacOS and Linux. I literally have no access to a Windows 10 box to even test this...

Okay, well, it looks like the package itself runs fine on Windows (and there's no reason it shouldn't). So something is goofed up with Meteor's `add` functionality on Windows. I'll...

Good to know. For me the mystery is: a) 1.5.1 install works fine on OS X and Linux b) No job-collection code actually runs during `meteor add` c) job-collection itself...

job-collection doesn't require node-gyp. There are no binary dependencies. And the dependencies didn't change (except for minor revs) between 1.4.0 and 1.5.1 ```sh meteor show vsivsi:[email protected] # Depends on: #...