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
i am confronted to an unsolved problem when I want to import external react libs (e.g. material-ui among others). it works well with npm run start (or webpack-serve ./webpack.serve.config.js -hot) but not with npm run build:all (or venv/bin/python usage.py) as it cannot find _react.default.createContext();.
debugging the webpack-serve version (which works) i can see that the function is in react.development.js:1266
while with venv/bin/python usage.py i have the following stacktrace:
at eval (FormControlContext.js?f516:15)
at Object../node_modules/@material-ui/core/FormControl/FormControlContext.js (enter_triggered_text_input.dev.js?v=0.0.1&m=1543579949:241)
at __webpack_require__ (enter_triggered_text_input.dev.js?v=0.0.1&m=1543579949:21)
at eval (InputBase.js?f12e:34)
at Object../node_modules/@material-ui/core/InputBase/InputBase.js (enter_triggered_text_input.dev.js?v=0.0.1&m=1543579949:301)
at __webpack_require__ (enter_triggered_text_input.dev.js?v=0.0.1&m=1543579949:21)
at eval (index.js?26dc:15)
at Object../node_modules/@material-ui/core/InputBase/index.js (enter_triggered_text_input.dev.js?v=0.0.1&m=1543579949:325)
at __webpack_require__ (enter_triggered_text_input.dev.js?v=0.0.1&m=1543579949:21)
at eval (Input.js?3722:22)
i am confronted to an unsolved problem when I want to import external react libs (e.g. material-ui among others). it works well with
npm run start
(orwebpack-serve ./webpack.serve.config.js -hot
) but not withnpm run build:all
(orvenv/bin/python usage.py
) as it cannot find_react.default.createContext();
.debugging the
webpack-serve
version (which works) i can see that the function is inreact.development.js:1266
while with
venv/bin/python usage.py
i have the following stacktrace:Originally posted by @qubolino in https://github.com/plotly/dash-docs/issues/194#issuecomment-443241827
The text was updated successfully, but these errors were encountered: