cannot find module /auth/ui
After upgrading from wasp 0.14.0 to 0.15.0 to 0.16.0 and run "wasp start", I get a blank screen and this error "Cannot find module '/Users/blahblahblah/app/.wasp/out/sdk/wasp/dist/client/auth/ui' imported from /Users/blahblahblah/app/.wasp/out/sdk/wasp/dist/client/auth/index.js".
Any suggestions on how to fix this? Thanks.
3 Replies
Hi @Kynetix. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
It seems you're encountering an issue after upgrading Wasp versions. This error is likely related to changes in the import paths for authentication components. Based on the information provided in the knowledge sources, I can suggest a solution:
The import path for authentication components has changed in newer versions of Wasp. Instead of importing from 'wasp/auth', you should now import from 'wasp/client/auth'.
To fix this issue, you need to update your import statements in your client-side code. Here's what you should do:
1. Look for any imports in your client-side code (especially in your auth-related pages) that are importing from 'wasp/auth'.
2. Change these imports to use 'wasp/client/auth' instead.
For example, if you have a login page, you might need to update it like this:
This change is mentioned in the Wasp documentation, which shows the correct import path for auth components.
After making these changes, try running
wasp clean to clear any cached builds, and then wasp start again. This should resolve the module not found error.
If you continue to experience issues after making these changes, you may want to double-check that all your files were properly migrated during the upgrade process. Some users have reported that the migration script didn't convert all paths correctly, especially those using @shared/ paths.
Discord support thread suggests that running the migration script again or manually checking and updating your import paths might be necessary.
If the problem persists, you might want to try a clean installation by removing the .wasp folder, node_modules, and package-lock.json, then running wasp start again to rebuild everything from scratch.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Kynetix, 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?@Kynetix can you share the code this is affecting?
There shouldn't be any changes from 0.14.0 to 0.16.0 that would case this kind of error. Could you share the full error message here? A screenshot maybe?