docs: RxJS v5.5 for plunkers and systemjs config

[wardbell]

URGENT - please merge ASAP as we have very little time to update docs before next NG release.

Should have been companion to PR #19985

PROBLEM: Doesn't work! Not building plunkers with RxJS v.5.5.2.
Then when I patch it in a plunker, RxJS v5.2 umd , import { switchMap } from 'rxjs/operators/switchMap' says the umd does NOT have /operators.

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] angular.io application / infrastructure changes
[ ] Other... Please describe:

[mary-poppins]

You can preview 8e8faa8 at https://pr20001-8e8faa8.ngbuilds.io/.

[gkalpak]

I can't reproduce the problem you mention in plnkrs. Can you post an example of a plnkr that throws the umd does NOT have /operators error?
Other than that LGTM.

[mlc-mlapis]

@gkalpak ... it is related to ReactiveX/rxjs#2971 (comment)

[gkalpak]

@mlc-mlapis, related or not I couldn't reproduce it ¯\_(ツ)_/¯.
Can you post an example plnkr that throws the error?

[sarunint]

I think @wardbell intended to say that the examples cannot using the "lettable operators" at the moment.

Reproduction: https://plnkr.co/edit/d0c7m11XUAIZLxY1gcVT (see hero-detail.component.ts)

I think this can be fixed by adding this line to systemjs.config.js:

'rxjs/operators': 'npm:rxjs@5.5.2/operators/index.js',

[gkalpak]

I see. But you can still do:

import {switchMap} from 'rxjs/operators/index';
// or
import {switchMap} from 'rxjs/operators/switchMap';

And with 'rxjs/operators': 'npm:rxjs@5.5.2/operators/index.js', you can indeed import for rxjs/operators.

So, there shouldn't be anything blocking further changes (or this PR). Is that correct, @wardbell?

[IgorMinar]

@wardbell @gkalpak going forward we should be using all operators only from rxjs/operators, no deep imports like rxjs/operators/operators.

[IgorMinar]

Can you also update the yarn.lock to use 5.5.2? Otherwise lgtm.

[IgorMinar]

Can you also update the yarn.lock to use 5.5.2? Otherwise lgtm.

I meant the examples yarn.lock file not the aio one.

[Foxandxss]

Closing this. I will put this changes with more upgrades for v5.

[angular-automatic-lock-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.}