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.
WANTED: Means of having deprecation messages only in development build
See original GitHub issueThere are methods of doing things we want to warn people are going to be deprecated in upcoming major releases of RxJS. Currently we don’t have anything in place to report these problems to the user in such a way that it doesn’t intrude on production.
Ideally a solution for this would:
- report that deprecated features are being used on build if the user is bundling somehow (Angular CLI, Webpack, etc)
- warn in console that deprecated features are being used, but only when
Rx.min.jswas being used - Not intrude or spam in production apps, or at leas do so as minimally as possible.
Looking for any thoughts, ideas or prior knowledge of how to go about this. Especially from other library owners that may have already solved this problem.
This is a critcal thing for RxJS to advance in the most friendly way possible
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (7 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
yup
process.env.NODE_ENV !== 'production'is the way to go.I think that modern IDEs are taking care of some of this… and I believe that lint rules can do some of the work here as well. Closing for now.