Could not resolve "@emotion/styled" imported by "@mui/styled-engine"
Hello, i get the above error when using a component that i have installed via npm, i have tried "npm i @emotion/react @emotion/styled" but this does not seem to help, any advice? Thank you very much.
7 Replies
Hi @Ertan Köse. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Hmm, I don't know enough to give you a confident answer yet. The knowledge sources provided do not contain information about resolving issues with "@emotion/styled" or "@mui/styled-engine". It would be best to refer to the official documentation or community forums of these libraries for more specific help.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Ertan Köse, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
@kapa.ai Get me some human experts plz
Let me check the knowledge base for you. One moment! :books:
----------------------
I'm sorry for any confusion, but as an AI, I don't have the ability to connect you with human experts directly. However, I can suggest a few places where you can seek help:
1. Wasp Discord Channel: The Wasp community is quite active on Discord and you can find help from other Wasp users and the Wasp team there. Here is the link to the Wasp Discord channel (https://discord.gg/rzdnErX).
2. Github Issues: If you're facing a specific issue with Wasp, you can check if similar issues have been reported or resolved in the Wasp Github repository (https://github.com/wasp-lang/wasp/issues).
Remember to provide as much detail as possible about your issue when seeking help, including any error messages and the steps you've taken to try to resolve the issue. This will make it easier for others to understand your problem and provide assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Ertan Köse, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
I had this exact same issue, it was resolved when I navigated into the app directory before doing npm i @emotion/react @emotion/styled. Have you tried that yet?
Yes unfortunately didn't help so i think the issue might lie somewhere else. Thank you tho.
Solved: Restarting my pc solved the issue..
You were in open-saas I believe, so yes it would be important to be in the
app dir!
Oh wow didn't expect that! What is your setup: Win with WSL? Any more issues? So sometimes we recommend doing wasp clean if stuff gets messed up on the Wasp side, but restarting your PC, that is a bit surprising.Yes Win with WSL, no more issues but the issue itself was persistent across new installs of saas template, perhaps wasp clean could have done the job.