Closed bukowskiadam closed 2 years ago
Hi there,
I get this warning from redux introduced in https://github.com/reactjs/redux/pull/1075 on my app with production build.
I've included redux-mock-store by accident in production build. It seems that during your build process for es module you replace NODE_ENV to development which gets replaced in included redux.
development
Steps to reproduce
npm run build:es
dist/index-es.js
if ("development" !== 'production' && typeof isCrushed.name === 'string' && isCrushed.name !== 'isCrushed') {
When I include redux-mock-store, then in production build it always gives this warning.
redux-mock-store
Solution
Probably you should not replace NODE_ENV for es module like redux does this. Ref: https://github.com/reactjs/redux/blob/55e77e88c98723f1883929458bb0144430108143/package.json#L25 https://github.com/reactjs/redux/blob/55e77e88c98723f1883929458bb0144430108143/rollup.config.js#L12
Hi there,
I get this warning from redux introduced in https://github.com/reactjs/redux/pull/1075 on my app with production build.
I've included redux-mock-store by accident in production build. It seems that during your build process for es module you replace NODE_ENV to
development
which gets replaced in included redux.Steps to reproduce
npm run build:es
dist/index-es.js
, line 205:When I include
redux-mock-store
, then in production build it always gives this warning.Solution
Probably you should not replace NODE_ENV for es module like redux does this. Ref: https://github.com/reactjs/redux/blob/55e77e88c98723f1883929458bb0144430108143/package.json#L25 https://github.com/reactjs/redux/blob/55e77e88c98723f1883929458bb0144430108143/rollup.config.js#L12