File: CHANGELOG.md

package info (click to toggle)
node-async-limiter 2.0.0-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, sid
  • size: 240 kB
  • sloc: makefile: 2
file content (33 lines) | stat: -rw-r--r-- 1,058 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
# Changelog

### v2.0.0 (2019-11-20)

> **This release contains minor breaking changes. These changes should not affect most applications.**

#### Breaking:

- Jobs will not start until the next tick (`process.nextTick`) after the first job is added. 
This allows you to order multiple jobs synchronously without unexpected effects.

This should align the limiter closer to programmer expectations, but
is technically breaking: the current code will immediately begin executing
the first job as soon as it is pushed.

This change also fixes a few edge-case bugs related to ordering & sync jobs:

- If an `onDone()` callback were added before any jobs were added in the same
tick, it would be immediately called.
- If a synchronous job were added, it would immediately execute completely
and potentially call `onDone()`.

#### Other changes:
- Internals refactoring
- Fix example calling `start()` (queue starts automatically)

### v1.0.1 (2019-08-02)

- Add `coverage` folder to npmignore for smaller bundle

### v1.0.0 (2017-09-11)

- Initial implementation