-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add option to suppress minified build warning #1548
Comments
Afaik MobX follows the exact same pattern as React here. React will give the same error if I am not mistaken? |
It sure used to. I think that's no longer the case. |
@jtheisen Fork it and remove the offending check? |
Or https://www.npmjs.com/package/patch-package, it's awesome! |
i'm also having this issue, but i can't figure out how else to express how productive i want my node env to be:
how can i satisfy the warning and fix my bundle? edit: hey hey, i think i figured it out.. the following works:
the difference that made it work, was simple changing the apparently that makes it globally affect the bundling or something |
@chase-moskal That comment is for the browserify project. Not MobX. |
@avioli -- well sure, but i was reacting to this warning coming out of mobx:
in my case, my answer was to change a browserify flag hopefully some folks in my situation will find this tip cheers |
If somebody wants to add a |
fix: add a configure env variable to mute minification warning (fix #1548)
See release notes of 4.8.0 / 5.8.0, it is now possible to override this using a global env variable (make sure to configure it in your build setup) |
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 or questions. |
MobX doesn't like to be minified while not having the NODE_ENV set to production:
I want both minification and keeping the React logging which won't happen with the suggested setting.
I don't think performance will be an issue for me.
Is there a way to get rid of that warning?
The text was updated successfully, but these errors were encountered: