Eliminate @reactivex/rxjs?
See original GitHub issueCurrently we release two packages:
@reactivex/rxjs
rxjs
Right now, the vast, vast majority of users are using rxjs
, not @reactivex/rxjs
. The major difference between the two used to be that the @reactivex/rxjs
one had more builds in it and the original source… however as of 5.5, we have all module build styles in rxjs
to support bundlers, and we have the src to support source maps. So they’re effectively not that much different anymore.
Should we deprecate @reactivex/rxjs
in favor of rxjs
?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:10
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Reduce operator - ReactiveX
The Reduce operator applies a function to the first item emitted by the source Observable and then feeds the result of the function...
Read more >reduce - Learn RxJS
Reduces the values from source observable to a single value that's emitted when the source completes. Just like Array.prototype.reduce() .
Read more >reduce - RxJS
Like Array.prototype.reduce(), reduce applies an accumulator function against an accumulation and each value of the source Observable (from the past) to ...
Read more >The RxJS library - Angular
Reactive programming is an asynchronous programming paradigm concerned with data streams and the propagation of change (Wikipedia). RxJS (Reactive ...
Read more >@reactivex/rxjs | Yarn - Package Manager
Important: This documentation covers modern versions of Yarn. For 1.x docs, see classic.yarnpkg.com. Yarn.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
do not forget we have rxjs-es too: https://github.com/ReactiveX/rxjs/issues/2218
I’m voting to deprecate except main one.
With all the build styles available in the
rxjs
name, I’m in favor of deprecating@reactivex/rxjs
. It’s what I use today and teach others to use.