Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Move `rxjs/add/*` modules to a separate package for 6.0?
See original GitHub issueMost of us are in agreement that we’d advise people use the pipeable operators instead of the prototype patching for a variety of reasons that have been outlined elsewhere.
Do we want to keep the rxjs/add/* modules in the same package as everything else, or do we want to have a separate package to support dot-chaining on NPM?
Or… more extreme… should we eliminate them? Maybe even wait for v 7 for that?
Either way, how could we best educate people of the caveats?
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This is done. We effectively did this with
rxjs-compat.yes, I’m sort of agreeing to separate packages, especially given size constraint we’d like to achieve in pkg. Either case it’ll be huge breaking so through guide / migration process should be prepared.