Replies: 1 comment
-
That is an error thrown from eslint no-undef rule, neither webpack nor qiankun. |
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!
This call is a follow-up for: #1691
I still get problems with having the webpack_public_path variable.
When starting the sub-application, which is still a "react" one, i get the following error in the console:
In my subApplication there's the entry point's configuration:
.rescriptsrc.js:
And the main application:
Can anyone tell me or lend me a tipp about why the problematic variable of wepack is still not exposed anywhere?
Happy for any tipps, thank you!
Beta Was this translation helpful? Give feedback.
All reactions