BREAKING CHANGE: The request '...' failed to resolve only because it was resolved as fully specified (probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"'). #373
-
Hi there, we recently tried to upgrade our asset pipeline from webpack5 to shakapacker 7, but get now following errors:
We are not really asset pipeline experts and asset compilation changes are always a horror task for our team (yay javascript eco system :D).. Any suggestions how I can fix this? Thank you so much! ❤️ |
Beta Was this translation helpful? Give feedback.
Answered by
Judahmeek
Oct 25, 2023
Replies: 1 comment 1 reply
-
Take a look at mui/material-ui#23744 and mui/material-ui#23290. This isn't a shakapacker or webpack bug. It's material-ui. |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
Judahmeek
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Take a look at mui/material-ui#23744 and mui/material-ui#23290.
This isn't a shakapacker or webpack bug. It's material-ui.