Replies: 1 comment
-
I seem to have found the solution to this problem myself: If you create a react app with npx create-react-app, the webpack and it's own webpack.config.js is delivered to you. This means, that you're local webpack.config.js won't be evaluated at all ... So it's either overwriting the configuration by hand, or with plugins or you create the react app by hand and configure webpack by yourself. So in that case, this case can be closed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello!
I am trying to get qiankun to run with one subApp.
The main and subApp are both react-apps, created with npx create-react-app.
The main app starts just fine, but with the subApp, there seems to be a problem, which may be more related with webpack than with qiankun.
Either way: Any help is much appreciated!
npm WARN [email protected] requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-deFailed to compile.
src\public-path.js
Line 2:5: 'webpack_public_path' is not
defined no-undef
Search for the keywords to learn more about each error.
I get the feeling that my webpack.config.js in the applications root directory is not registered properly, since i can add nonsense characters in it without the webpack even noticing.
That's my webpack.config.js at the moment where i tried to set the publicPath / webpack_public_path:
My question is:
Where do i set the 'webpack_public_path' variable beforehand to resolve the issue with my subApp? In the documentation is stated, that you have to declare it in the entry point of the application, which is index.js for me. But that didn't really help either.
Thank you for your help!
Beta Was this translation helpful? Give feedback.
All reactions