Materuial-UI namespace import is not defined #14798
Unanswered
dvakatsiienko
asked this question in
Help
Replies: 2 comments
-
Beta Was this translation helpful? Give feedback.
0 replies
-
I've changed the import type from namespace to named only for this particular file, and build succeeded. |
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Bug report
We use namespace approach to import
Material-UI
components across entire app like so:Recently a
next build
command started to produce the following output:It is very odd because previously the build were fine (we migrated entire app from CRA couple of weeks ago) — the compilation was okay and at some point this issue appeared. The thing is that we have entire application stitched with this kind of imports, and the build output does not give any trails to look where.
Next.js version: 9.4.4
Does anyone had this problem?
It is possible to debug with better tracing details?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions