Vaughn Iverson

Hi, don't instantiate a new collection with every click. Move this code outside of your event handler: `const jobQueue = JobCollection('jobQueue', { noCollectionSuffix: true });`

Hi, thanks for this. I'm not a Typescript user but just looking at it I can tell that you put a nontrivial amount of work into those declarations! My main...

At first glance, DefinitelyTyped seems like the way to go. Any drawbacks to that approach that you can think of?

You have a classic job dependency here. Sounds like you don't really want a delay of 5 (or whatever) minutes, you simply want job2 to wait until job1 is successfully...

`fibers` is *dev* dependency because `meteor-job` supports running in node.js, outside of Meteor, but with Fibers. The *dev* dependency is required for code coverage of the Fibers dependent functionality that...

Right, I remember now. This was literally issue #1 on this package. The client side of JobCollection in Meteor also has a dependency on the meteor-job npm package, and prior...

If Meteor's package publishing process causes npm dev-only dependencies to be included, that is a bug in Meteor.

Hmm, it's possible that maybe it picked it up because I had run unit tests out of the same directory I published from... Unfortunately my dev box is about 4000...

Yes, I'm planning a quick release in the next day or two.

job-collection 1.5.2 is on Atmosphere now. I have verified that it was published without any dev dependencies installed in the meteor-job submodule (including fibers), so hopefully this will clear-up the...