Curious what's next for RxJS? Follow along with Issue 6367.

Reactive Extensions Library for JavaScript. This is a rewrite of Reactive-Extensions/RxJS and is the latest production-ready version of RxJS. This rewrite is meant to have better performance, better modularity, better debuggable call stacks, while staying mostly backwards compatible, with some breaking changes that reduce the API surface.

Apache 2.0 License

• Code of Conduct
• Contribution Guidelines
• Maintainer Guidelines
• API Documentation

• master - This is all of the current work, which is against v7 of RxJS right now
• 6.x - This is the branch for version 6.X

Most PRs should be made to master.

By contributing or commenting on issues in this repository, whether you've read them or not, you're agreeing to the Contributor Code of Conduct. Much like traffic laws, ignorance doesn't grant you immunity.

npm install rxjs

It's recommended to pull in the Observable creation methods you need directly from 'rxjs' as shown below with range. And you can pull in any operator you need from one spot, under 'rxjs/operators'.

import { range } from "rxjs";
import { map, filter } from "rxjs/operators";

range(1, 200)
  .pipe(
    filter(x => x % 2 === 1),
    map(x => x   x)
  )
  .subscribe(x => console.log(x));

For CDN, you can use unpkg:

https://unpkg.com/rxjs@^7/dist/bundles/rxjs.umd.min.js

The global namespace for rxjs is rxjs:

const { range } = rxjs;
const { map, filter } = rxjs.operators;

range(1, 200)
  .pipe(
    filter(x => x % 2 === 1),
    map(x => x   x)
  )
  .subscribe(x => console.log(x));

• Smaller overall bundles sizes
• Provide better performance than preceding versions of RxJS
• To model/follow the Observable Spec Proposal to the observable
• Provide more modular file structure in a variety of formats
• Provide more debuggable call stacks than preceding versions of RxJS

• npm run compile build everything
• npm test run tests
• npm run dtslint run dtslint tests

We appreciate all contributions to the documentation of any type. All of the information needed to get the docs app up and running locally as well as how to contribute can be found in the documentation directory.