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
So, later on in the same file we reference it to decide whether to log warnings (using warnTimeout), and even in production builds we are seeing these logs:
console.error(`warning: in logic for type(s): ${stringifyType(type)} - dispatchMultiple is always true in next version. For non-ending logic, set warnTimeout to 0`);
}
I have a couple questions regarding the way we define NODE_ENV here:
why do we check for typeof window === 'undefined'? Is this just meant for the build/babel step?
I'm using CRA, can't overwrite NODE_ENV. Do you have a suggestion how to approach this?
The text was updated successfully, but these errors were encountered:
I ran into this issue where
NODE_ENV
is always!== "production"
, because when running in the browserwindow
won't beundefined
.Check the code below:
redux-logic/src/createLogic.js
Line 24 in 1034a3e
So, later on in the same file we reference it to decide whether to log warnings (using
warnTimeout
), and even in production builds we are seeing these logs:redux-logic/src/createLogic.js
Lines 188 to 193 in 1034a3e
I have a couple questions regarding the way we define
NODE_ENV
here:typeof window === 'undefined'
? Is this just meant for the build/babel step?NODE_ENV
. Do you have a suggestion how to approach this?The text was updated successfully, but these errors were encountered: