Thanks for this. I think it looks good, but anyone else want to chime in?

@timdorr The thing to verify is that those blocks still get removed in the prod build. I suppose comparing the prod build size before and after this change would work.

Yep, I'll want to verify locally to be sure. I'll try to run that through tonight or tomorrow at some point.

@jimbolla @timdorr the way react does this check is by defining a __DEV__ variable. Chances are you already knew this. Although I don't know how to define this globally, we can still define something like this in index.js file and export from there to check if(__DEV__) , I think this would be a cleaner solution? I would be glad to implement this, and also would like to work on this library for self-improvement. I would be happy if I can contribute, even if it's a small change :)

@kaushik94 That's transformed into a NODE_ENV check during the build process. They use it as a shorthand while coding, but it's not how the build comes out compiled.

I checked against the production build, and they are still sticking around in the UMD build, unfortunately. I'm not sure there is a good way to fix this internally at the moment.

I would instead either use the UMD version or "polyfill" with window.process = { env: 'production' } before importing.