update RxJS peer dependency to 5.0.0-rc.4

We are currently depending on 5.0.0-beta.12. The only significant breaking change between beta.12 and rc.4 seems to be the removal of thecache operator.

We can either upgrade now and get this into 2.3.0 (feature freeze this Wednesday) or wait until the next major release due in March. I’d prefer 2.3 if cache operator removal is the only significant breaking change.

The list of things to do:

• update the main package.json and shrinkwrap files
• update all package specific package.json files under modules/@angular/
• upgrade google3 with rc.4 (currently on rc.2) - @alexeagle working on this already, ETA tomorrow
• figure out what to do about the cache operator for people that depend on it - one option is to create a gist that people could paste into their apps (or create an npm package, but we don’t want to maintain that and we’d have to create a umd bundle in addition to d.ts and other stuff => gist is a much better option IMO) - if we do go with gist, then we should create the TS and ES5 version to cover pretty much all the scenarios.
• ping angular-cli to make sure they are aware of this change // @hansl
• ping docs team to make sure that they are aware of this change // @wardbell

I believe that’s it.

[hansl]

In master, but not on NPM. Which implies that everyone using Angular will be stuck to rc.4 until March, and even then they’ll have to upgrade their Angular major version.

Which means that Angular 2.x will (forever) be stuck with RxJS rc.4. Correct?

I think that makes a greater case for loose versioning and/or 2.4 being released when RxJS is final. It’s unreasonable to deny every Angular apps to use the final version of RxJS.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}