You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My app is build from react-transform-boilerplate.git. For developing I use nodejs and webpack and all is ok. But for production I dont use Nodejs. App loads via classic script tag in html <div id="app"></div><scipt src="js/react-app.js"></script>
like other frontends js libraries. I dont need index for Google and app is part of classic PHP web.
App works but in console I get message:
You are currently using minified code outside of NODE_ENV === 'production'. This means that you are running a slower development build of Redux. You can use loose-envify (https://github.com/zertosh/loose-envify) for browserify or DefinePlugin for webpack (http://stackoverflow.com/questions/30030031) to ensure you have the correct code for your production build.
I really dont know how to solve this. Is there some workaround?
The text was updated successfully, but these errors were encountered:
It's a common source of confusion, no worries! Envifying is important for React anyway so we just followed the convention most people were already using.
Hello,
I dont know is this right place but I try.
My app is build from react-transform-boilerplate.git. For developing I use nodejs and webpack and all is ok. But for production I dont use Nodejs. App loads via classic script tag in html
<div id="app"></div><scipt src="js/react-app.js"></script>
like other frontends js libraries. I dont need index for Google and app is part of classic PHP web.
App works but in console I get message:
You are currently using minified code outside of NODE_ENV === 'production'. This means that you are running a slower development build of Redux. You can use loose-envify (https://github.com/zertosh/loose-envify) for browserify or DefinePlugin for webpack (http://stackoverflow.com/questions/30030031) to ensure you have the correct code for your production build.
I really dont know how to solve this. Is there some workaround?
The text was updated successfully, but these errors were encountered: