-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: No more KitchenSink #1650
Comments
I'm in favor of this in general too, but had assumption those packages are similar representation of |
Agreed. |
Been in favor of this for a long time, let's do it. |
Yes. If someone cares that much they should be using bundling and tree shaking anyhow. |
closes ReactiveX#1650 BREAKING CHANGE: `Rx.kitchenSink` and `Rx.DOM` are not removed, `Rx` exports everything.
closes ReactiveX#1650 BREAKING CHANGE: `Rx.kitchenSink` and `Rx.DOM` are removed, `Rx` export everything.
I would love to see this go out in a beta 8. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
We should probably just have one global export file for the masses.
If people are using the global export version of RxJS, it can be assumed that they're probably hacking around, and/or not really serious about reducing the size of their downloaded application.
At this point it's a little confusing to say "this is in Rx, but this is in Kitchensink" to people. Also, given how modular this library is, it would be easy enough for anyone to make their own custom build of RxJS 5 to keep around.
Basically the idea is just to put everything in Rx.ts
Thoughts?
The text was updated successfully, but these errors were encountered: