amqplib - npm Package Versions

Changes in v0.1.3 (since v0.1.2)

git log v0.1.2..v0.1.3

Enhancements

• Add support in the API for using Basic.Reject rather than Basic.Nack, the latter of which is a RabbitMQ extension and not in older versions of RabbitMQ.

Changes in v0.1.2 (since v0.1.1)

git log v0.1.1..v0.1.2

Fixes

• Restore support for publishing zero-length messages

Enhancements

• Recognise [authentication failures][rabbitmq-auth-failure]
• An option to set TCP_NODELAY on connection sockets

Changes in v0.1.1 (since v0.1.0)

git log v0.1.0..v0.1.1

Fixes

• Safer frame construction, no longer relies on allocating a large, fixed-size buffer and hoping it's big enough
• The ports of RabbitMQ tutorials now avoid a race between publishing and closing the connection

Enhancements

• Support for RabbitMQ's consumer priority extension
• Support for RabbitMQ's connnection.blocked extension
• Better write speed from batching frames for small messages
• Other minor efficiency gains in method encoding and decoding
• Channel and connection state errors (e.g., trying to write when closed) include a stack trace from when they moved to that state
• The arguments table, passed as an option to some methods, can include fields in its prototype chain
• Provide the more accurately named persistent as a near equivalent of deliveryMode

Changes in v0.1.0 (since v0.0.2)

git log v0.0.2..v0.1.0

Breaking changes

• Consumer callbacks are invoked with null if the consumer is cancelled (see [RabbitMQ's consumer cancel notification][rabbitmq-consumer-cancel])
• In confirm channels, instead of #publish and #sendToQueue returning promises, they return a boolean as for normal channels, and take a Node.JS-style function (err, ok) callback for the server ack or nack

Fixes

• Overlapping channel and connection close frames are dealt with gracefully
• Exceptions thrown in consumer callbacks are raised as 'error' events
• Zero-size messages are handled
• Avoid monkey-patching Buffer, and eschew require('util')._extend

Enhancements

• Channels now behave like Writable streams with regard to #publish and #sendToQueue, returning a boolean from those methods and emitting 'drain'
• Connections now multiplex frames from channels fairly
• Low-level channel machinery is now fully callback-based

Changes in v0.1.0 (since v0.0.2)

git log v0.0.2..v0.1.0

Breaking changes

• Consumer callbacks are invoked with null if the consumer is cancelled (see [RabbitMQ's consumer cancel notification][rabbitmq-consumer-cancel])
• In confirm channels, instead of #publish and #sendToQueue returning promises, they return a boolean as for normal channels, and take a Node.JS-style function (err, ok) callback for the server ack or nack

Fixes

• Overlapping channel and connection close frames are dealt with gracefully
• Exceptions thrown in consumer callbacks are raised as 'error' events
• Zero-size messages are handled
• Avoid monkey-patching Buffer, and eschew require('util')._extend

Enhancements

• Channels now behave like Writable streams with regard to #publish and #sendToQueue, returning a boolean from those methods and emitting 'drain'
• Connections now multiplex frames from channels fairly
• Low-level channel machinery is now fully callback-based