[](https://travis-ci.org/Reactive-Extensions/RxJS) [](https://david-dm.org/Reactive-Extensions/RxJS#info=dependencies) [](https://david-dm.org/Reactive-Extensions/RxJS#info=devDependencies) [](http://badge.fury.io/js/rx) [](http://gruntjs.com/) [](https://bitdeli.com/free "Bitdeli Badge") **[The Need to go Reactive](#the-need-to-go-reactive)** | **[About the Reactive Extensions](#about-the-reactive-extensions)** | **[Batteries Included](#batteries-included)** | **[Why RxJS?](#why-rxjs)** | **[Dive In!](#dive-in)** | **[Resources](#resources)** | **[Getting Started](#getting-started)** | **[What about my libraries?](#what-about-my-libraries)** | **[Compatibility](#compatibility)** | **[Contributing](#contributing)** | **[License](#license)** # The Reactive Extensions for JavaScript (RxJS) 2.2... # *...is a set of libraries to compose asynchronous and event-based programs using observable collections and Array#extras style composition in JavaScript* The project is actively developed by Microsoft Open Technologies, Inc., in collaboration with a community of open source developers. This project is a mirror of the [CodePlex](http://rxjs.codeplex.com/) repository. ## The Need to go Reactive ## Reactive Programming is a hot topic as of late, especially with such things as the [Reactive Manifesto](http://www.reactivemanifesto.org/). Applications, especially on the web have changed over the years from being a simple static page, to DHTML with animations, to the Ajax revolution. Each time, we're adding more complexity, more data, and asynchronous behavior to our applications. How do we manage it all? How do we scale it? By moving towards "Reactive Architectures" which are event-driven, resilient and responsive. With the Reactive Extensions, you have all the tools you need to help build these systems. ## About the Reactive Extensions ## The Reactive Extensions for JavaScript (RxJS) is a set of libraries for composing asynchronous and event-based programs using observable sequences and fluent query operators that many of you already know by Array#extras in JavaScript. Using RxJS, developers represent asynchronous data streams with Observables, query asynchronous data streams using our many operators, and parameterize the concurrency in the asynchronous data streams using Schedulers. Simply put, RxJS = Observables + Operators + Schedulers. Whether you are authoring a web-based application in JavaScript or a server-side application in Node.js, you have to deal with asynchronous and event-based programming as a matter of course. Although some patterns are emerging such as the Promise pattern, handling exceptions, cancellation, and synchronization is difficult and error-prone. Using RxJS, you can represent multiple asynchronous data streams (that come from diverse sources, e.g., stock quote, tweets, computer events, web service requests, etc.), and subscribe to the event stream using the Observer object. The Observable notifies the subscribed Observer instance whenever an event occurs. Because observable sequences are data streams, you can query them using standard query operators implemented by the Observable type. Thus you can filter, project, aggregate, compose and perform time-based operations on multiple events easily by using these our many operators. In addition, there are a number of other reactive stream specific operators that allow powerful queries to be written. Cancellation, exceptions, and synchronization are also handled gracefully by using the methods on the Observable object. But the best news of all is that you already know how to program like this. Take for example the following JavaScript code, where we get some stock data and then manipulate and then iterate the results. ```js /* Get stock data somehow */ var source = getStockData(); source .filter(function (quote) { return quote.price > 30; }) .map(function (quote) { return quote.price; }) .forEach(function (price) { console.log('Prices higher than $30: $' + price); }); ``` Now what if this data were to come as some sort of event, for example a stream, such as as a WebSocket, then we could pretty much write the same query to iterate our data, with very litle change. ```js /* Get stock data somehow */ var source = getAsyncStockData(); var subscription = source .filter(function (quote) { return quote.price > 30; }) .map(function (quote) { return quote.price; }) .subscribe( function (price) { console.log('Prices higher than $30: $' + price); }, function (err) { console.log('Something went wrong: ' + err.message); }); /* When we're done */ subscription.dispose(); ``` The only difference is that we can handle the errors inline with our subscription. And when we're no longer interested in receiving the data as it comes steraming in, we call `dispose` on our subscription. ## Batteries Included ## This set of libraries include: - [rx.lite.js](doc/libraries/rx.lite.md) - lite version with event bindings, creation, time and standard query operators with a compat file for older browsers. - [rx.js](doc/libraries/rx.md) - core library for ES5 compliant browsers and runtimes plus compatibility for older browsers. - [rx.aggregates.js](doc/libraries/rx.aggregates.md) - aggregation event processing query operations - [rx.async.js](doc/libraries/rx.async.md) - async operationrs such as events, callbacks and promises plus a compat file for older browsers. - [rx.binding.js](doc/libraries/rx.binding.md) - binding operators including multicast, publish, publishLast, publishValue, and replay - [rx.coincidence.js](doc/libraries/rx.coincidence.md) - reactive coincidence join event processing query operations - [rx.experimental.js](doc/libraries/rx.experimental.md) - experimental operators including imperative operators and forkJoin - [rx.joinpatterns.js](doc/libraries/rx.joinpatterns.md) - join patterns event processing query operations - [rx.testing.js](doc/libraries/rx.testing.md) - used to write unit tests for complex event processing queries - [rx.time.js](doc/libraries/rx.time.md) - time-based event processing query operations - [rx.virtualtime.js](doc/libraries/rx.virtualtime.md) - virtual-time-based schedulers ## Why RxJS? ## One question you may ask yourself, is why RxJS? What about Promises? Promises are good for solving asynchronous operations such as querying a service with an XMLHttpRequest, where the expected behavior is one value and then completion. The Reactive Extensions for JavaScript unifies both the world of Promises, callbacks as well as evented data such as DOM Input, Web Workers, Web Sockets. Once we have unified these concepts, this enables rich composition. To give you an idea about rich composition, we can create an autocompletion service which takes the user input from a text input and then query a service, making sure not to flood the service with calls for every key stroke, but instead allow to go at a more natural pace. First, we'll reference the JavaScript files, including jQuery, although RxJS has no dependencies on jQuery... Next, we'll get the user input from an input, listening to the keyup event by using the `Rx.Observable.fromEvent` method. ```js var $input = $('#input'), $results = $('#results'); /* Only get the value from each key up */ var keyups = Rx.Observable.fromEvent($input, 'keyup') .map(function (e) { return e.target.value; }) .filter(function (text) { return text.length > 2; }); /* Now throttle/debounce the input for 500ms */ var throttled = keyups .throttle(500 /* ms */); /* Now get only distinct values, so we eliminate the arrows and other control characters */ var distinct = throttled .distinctUntilChanged(); ``` Now, let's query Wikipedia! In RxJS, we can instantly bind to any [Promises A+](https://github.com/promises-aplus/promises-spec) implementation through the `Rx.Observable.fromPromise` method or by just directly returning it, and we wrap it for you. ```js function searchWikipedia (term) { var promise = $.ajax({ url: 'http://en.wikipedia.org/w/api.php', dataType: 'jsonp', data: { action: 'opensearch', format: 'json', search: encodeURI(term) } }).promise(); } ``` Once that is created, now we can tie together the distinct throttled input and then query the service. In this case, we'll call `flatMapLatest` to get the value and ensure that we're not introducing any out of order sequence calls. ```js var suggestions = distinct .flatMapLatest(searchWikipedia); ``` Finally, we call the subscribe method on our observable sequence to start pulling data. ```js suggestions.subscribe( function (data) { var res = data[1]; /* Do something with the data like binding */ $results.empty(); $.each(res, function (_, value) { $('