This will cause npm to attempt to install hiredis when installing redis, but if the hiredis installation fails, it won't cause the redis install to abort. The optionalDependencies feature was added pretty much explicitly for the redis->hiredis use case. :)
* authentication retry while server is loading db (danmaz74) [GH-101] * command arguments processing issue with arrays New features: * Auto update of new commands from redis.io (Dave Hoover) * Performance improvements and backpressure controls. * Commands now return the true/false value from the underlying socket write(s). * Implement command_queue high water and low water for more better control of queueing. See `examples/backpressure_drain.js` for more information.
Bug fix for monitor mode. (forddg) Auto update of new commands from redis.io (Dave Hoover)
Run this: node generate_commands.js To fetch redis.io/commands.json and save it to a file that node_redis will read at startup.
Thanks to Dean Mao and Austin Chau.
When a Redis server starts up, it might take a while to load the dataset into memory. During this time, the server will accept connections, but will return errors for all non-INFO commands. Now node_redis will send an INFO command whenever it connects to a server. If the info command indicates that the server is not ready, the client will keep trying until the server is ready. Once it is ready, the client will emit a "ready" event as well as the "connect" event. The client will queue up all commands sent before the server is ready, just like it did before. When the server is ready, all offline/non-ready commands will be replayed. This should be backward compatible with previous versions. To disable this ready check behavior, set `options.no_ready_check` when creating the client. As a side effect of this change, the key/val params from the info command are available as `client.server_options`. Further, the version string is decomposed into individual elements in `client.server_options.versions`.
Thanks to Gustaf Sjöberg.
…p error properly.