smqp - npm Package Versions

5.0.0

Attempt to tweak performance by removing stuff. Consequently some things broke.

Breaking

• Remove support for node 10 (mochas fault)
• Message property consumerTag is removed, can be found by message.fields.consumerTag
• Message property messageId is removed, can be found by message.properties.messageId
• Remove onMessageQueued argument from queue.queueMessage function
• Remove queue.dequeueMessage(message) function
• Change routing key pattern hash (#) handling to /.*?/ from /.+?/

Fixes

• Fix pattern matching bug if more than one wildcard

4.0.0

For performance reasons the Broker has been prototyped. Thank you @roberto-naharro and co for discovering and resolving this (#5). This means that functions cannot be deconstructed and called without binding or using call/apply.

3.2.0

Slimmer and swifter state.

• getState: Only use JSON-fns when really necessary (= messages)
• Stop dead lettering messages when queue is deleted. Did some deep forrest coverage hunting and found no scenario when this has ever worked, maybe since it isn't part of RabbitMQ behaviour

3.1.0

Coverage hunting.

• Stop consumers when queue is stopped
• Remove setter for message consumerTag

3.0.1

• Sometimes you need the name of the event, especially if you listen with wildcards. The name is an exact match of the emitted message routing key.

3.0.0

Confirm messages and node 10 and above.

Breaking changes

• Drop nodejs 8 support, or at least for tests due to mocha

Additions

• New message confirm option, will emit message.nack, message.ack, or message.undelivered on broker
• Support offing broker events by consumerTag
• Support offing exchange events by consumerTag

2.2.0

• Add broker function getConsumers() to get the list of consumer properties

2.1.1

• Ignore published message if no one is listening, unless it is mandatory

2.1.0

• Support changing destination exchange key in shovel
• Support overwriting shoveled message properties