axetroy / equeue

a lib to build async task queue

queue.js

Description

a lib to build async task queue

Usage

npm install https://github.com/axetroy/queue.git --save

const Queue = require('@axetroy/queue')
// or
import Queue from '@axetroy/queue';

Documentation;

Contribution

git clone https://github.com/axetroy/queue.git
cd 
npm install gulp-cli -g
npm install mocha -g
npm install 

npm run build

Test

npm run test
// or
npm run test:watch

License

The MIT License (MIT)

Copyright (c) 2016 axetroy

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

equeue's Issues

An in-range update of ts-loader is breaking the build 🚨

Version 2.0.2 of ts-loader just got published.

Branch	Build failing 🚨
Dependency	ts-loader
Current Version	2.0.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As ts-loader is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v2.0.2

• Fix performance regression related to using getTimes() by tracking timestamps - thanks @wearymonkey

Commits

The new version differs by 8 commits .

• 8987ac6 v2.0.2 release prep
• 1c1e2c3 Update CHANGELOG.md
• 44a2cdb Track timestamps to filter changed files. (#500)
• 05ca5e5 Merge pull request #495 from johnnyreilly/master
• d364800 tolerate kb differences in comparison tests
• dedc468 Change test output to cater for change in webpack
• a7b7306 Merge pull request #491 from johnnyreilly/master
• 1d30c4e regenerate test data for conditionalRequire

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of yargs is breaking the build 🚨

Version 7.1.0 of yargs just got published.

Branch	Build failing 🚨
Dependency	yargs
Current Version	7.0.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As yargs is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 8 commits .

• e7359d6 chore(release): 7.1.0
• c357412 docs: switch to conventional commits badge [ci skip] (#850)
• 17e89bd fix: we shouldn't output help if we've printed a prior help-like message (#847)
• 50c9acd chore: add editorconfig (#848)
• 360e301 fix: get terminalWidth in non interactive mode no longer causes a validation exception (#837)
• fde0564 feat: add support for numeric commands (#825)
• c748dd2 fix: fix demandOption no longer treats 'false' as truthy (#829)
• e0b4efb test: Made unit test passing with node-chakracore

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of ts-node is breaking the build 🚨

Version 3.0.5 of ts-node just got published.

Branch	Build failing 🚨
Dependency	ts-node
Current Version	3.0.4
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As ts-node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 7 commits.

• c18331a 3.0.5
• 5cf97b1 Add --inspect-brk to known flags (#343)
• 7dfb3e3 Pin node tests at 6.x (#340)
• 633d537 chore(package): update chai to version 4.0.1 (#337)
• b751a56 Define exports and improve getTypeInfo help (#332)
• d018300 Update yn default option
• cc3bf22 Expose _ bin file for consumers to use

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of babel-core is breaking the build 🚨

Version 6.24.1 of babel-core just got published.

Branch	Build failing 🚨
Dependency	babel-core
Current Version	6.24.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-core is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

Version 7.0.9 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.8
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

Version 7.0.15 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.14
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/axetroy/equeue/builds/227731874?utm_source=github_status&utm_medium=notification)

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of @types/mocha is breaking the build 🚨

Version 2.2.41 of @types/mocha just got published.

Branch	Build failing 🚨
Dependency	@types/mocha
Current Version	2.2.40
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/axetroy/equeue/builds/226791476?utm_source=github_status&utm_medium=notification)

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of @types/chai is breaking the build 🚨

Version 3.5.1 of @types/chai just got published.

Branch	Build failing 🚨
Dependency	@types/chai
Current Version	3.5.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/chai is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

An in-range update of webpack is breaking the build 🚨

Version 2.3.3 of webpack just got published.

Branch	Build failing 🚨
Dependency	webpack
Current Version	2.3.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As webpack is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v2.3.3

Bugfixes:

• fix progress in multi compiler

Commits

The new version differs by 2 commits .

• ba24c1b 2.3.3
• 956f618 Fix ProgressPlugin for multi compiler caused by ES6 refactoring

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴