@onify/fake-amqplib 0.9.1 → 2.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +89 -29
- package/index.d.ts +60 -0
- package/index.js +451 -360
- package/main.cjs +591 -0
- package/package.json +30 -13
- package/CHANGELOG.md +0 -61
package/CHANGELOG.md
DELETED
|
@@ -1,61 +0,0 @@
|
|
|
1
|
-
Changelog
|
|
2
|
-
=========
|
|
3
|
-
|
|
4
|
-
# 0.9.0
|
|
5
|
-
|
|
6
|
-
- support connecting with urlish object
|
|
7
|
-
- smqp@6
|
|
8
|
-
|
|
9
|
-
# 0.8.5
|
|
10
|
-
|
|
11
|
-
- ack/nack all only cares about messages consumed by channel, previously everything was gone
|
|
12
|
-
|
|
13
|
-
# 0.8.4
|
|
14
|
-
|
|
15
|
-
- ack/nack all fix
|
|
16
|
-
|
|
17
|
-
# 0.8.3
|
|
18
|
-
|
|
19
|
-
- Call confirm channel callback when the message is queued, not when it is consumed!
|
|
20
|
-
- implement publish with empty string special case
|
|
21
|
-
- hide some internal props from message
|
|
22
|
-
|
|
23
|
-
# 0.8.2
|
|
24
|
-
|
|
25
|
-
- share behind the scenes broker if connection hosts and vhost are the same
|
|
26
|
-
- add new `connectSync` helper method to be able to get a connection synchronously to facilitate testing
|
|
27
|
-
|
|
28
|
-
# 0.8.1
|
|
29
|
-
|
|
30
|
-
- be a better mimic of amqplib, some stuff didn't work at all prior to this version
|
|
31
|
-
|
|
32
|
-
## Additions
|
|
33
|
-
|
|
34
|
-
- Handle different behaviours between RabbitMQ versions
|
|
35
|
-
|
|
36
|
-
# 0.8.0
|
|
37
|
-
|
|
38
|
-
- bump `smqp@5`
|
|
39
|
-
- stop building for node 10 (mocha's fault)
|
|
40
|
-
|
|
41
|
-
# 0.7.0
|
|
42
|
-
|
|
43
|
-
- bump `smqp@4`
|
|
44
|
-
|
|
45
|
-
# 0.6.0
|
|
46
|
-
|
|
47
|
-
- bump `smqp@3.2`
|
|
48
|
-
|
|
49
|
-
# 0.5.0
|
|
50
|
-
|
|
51
|
-
- support exclusive queue and its behaviour
|
|
52
|
-
- emit return on channel if mandatory message was not routed
|
|
53
|
-
|
|
54
|
-
# 0.4.0
|
|
55
|
-
|
|
56
|
-
- apparently connection is killed as well when trying to consume exclusive consumed queue
|
|
57
|
-
- try to mimic real behaviour and throw some errors with code
|
|
58
|
-
|
|
59
|
-
# 0.3.0
|
|
60
|
-
|
|
61
|
-
- kill channel if trying to consume exclusive consumed queue
|