RXJS lettable operators

[elvirdolic]

There are severals discussions around the rxjs imorts.

Does the CLI handle this correctly?

import {map} from 'rxjs/operators/map';

Vs

import {map} from 'rxjs/operators';

In which case does tree shaking work in CLI projects?

[kylecordes]

Functionally, this works great, my group is using it on multiple projects already.

We have not yet verified whether the tree shakes correctly with CLI; hopefully someone from the team can answer that part. It should do so, but there could be some tweak yet needed. (If you need to deploy shortly in a case where the bundle size is vital, just try it and see if it affects your bundle size.)

[elvirdolic]

We have changed everything to lettable imports like this: import {map} from 'rxjs/operators';

No change in payload after migration. This is the reason I was asking.

[devoto13]

Both ways should support tree shaking. In my case I get a slight bundle size increase when importing from rxjs/operators instead of long import (499K vs 496K), which is probably caused by inclusion of file with re-exports of all operators. In both cases source-map-explorer indicates that no extra operators are included.

[hccampos]

Shouldn't matter either way, but the terser version is way easier to maintain and read.

Anyway, in RxJS 6 you'll be able to import everything from 'rxjs' which will be awesome if it can be properly tree shaken.

[deebloo]

@elvirdolic like @devoto13 said it should work correctly

[Splaktar]

I also saw my bundle size increase by 10 KB as RxJS increased from 60 KB to 122 KB when using the new lettable operators. I also mentioned this in #8854 (comment). Still looking for the issue that is tracking this bundle increase bug.

[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.}