Will kendo release a version without rxjs-compat in the future (or depends on rxjs@^6.0.0)?
Second the question.
With rxjs-compat final app always has whole rxjs and rxjs-compat libs. Huge waste of resources.
We will drop support for RxJS 5.x after Angular 5 reaches EOL in April 2019.
@AlexGS74 rxjs-compat only contains re-exports and does not affect the bundle size. Check that you're not importing the full 'rxjs'. Check out Managing RxJS Imports with TSLint
for a few handy TSLint rules that guard against this.
RxJs 6 is tree shaking friendly and has huge potential of shaking unused code, which is impossible to utilize as long as rxjs-compat is in the bundle, thus the rxjs-compat increases the bundle size.
@AlexGS74 tree-shaking is made possible by pipeable operators which are available in 5.5+. These operators The legacy, global operators were removed entirely in 6.x
Thus, 6.x is always tree-shakable, while 5.5 and 6 + rxjs-compat are tree-shakeable as long as only pipeable operators are used. The Kendo UI components use only pipeable operators.
@tsvetomir Thank you for this clarification! Will re-evaluate my results once my project is moved to pipeable operators only.
Thanks for the info. Good to know you are just using the old imports. And thanks for the ts-lint link so I can enforce rjxs 6 best practices while using the compt lib.
Hi, it seems like @progress/kendo-angular-resize-sensor latest stable (3.2.0) still use rxjs-compat (while the 4.0.0-dev.201906030706 does not). Could you release a stable 3.x (or 4.x) free from rxjs-compat please?
This package has been merged with @progress/kendo-angular-common. Please update to the latest Kendo UI for Angular package versions and uninstall it.
This note has been added as a deprecation notice to the package on npm to help other users.
Most helpful comment
We will drop support for RxJS 5.x after Angular 5 reaches EOL in April 2019.
@AlexGS74 rxjs-compat only contains re-exports and does not affect the bundle size. Check that you're not importing the full 'rxjs'. Check out Managing RxJS Imports with TSLint
for a few handy TSLint rules that guard against this.