why does wasp not compile and keeps installing forever
I keep getting this error when I run
wasp db studio on a M1 macbook pro. It never installs.
5 Replies
Wohooo @macevilc, you just became a Waspeteer level 1!
Hi @macevilc. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information in the knowledge sources, there are a few common reasons why Wasp may not compile and appears to be "installing forever," especially on an M1 MacBook Pro:
1. Platform Compatibility (Apple Silicon / M1):
- Wasp's binary is built for x86, not arm64 (Apple Silicon). On M1/M2 Macs, you need to install Rosetta to run x86 binaries. If you haven't installed Rosetta, Wasp and its dependencies may not work correctly, leading to issues like endless installation or commands not responding. You can install Rosetta with:
Quick Start: Installation
2. Prisma Engine Binary Mismatch:
- When running
Wasp db studio not working? 3. Terminal/Process Issues: - If you run
wasp db studio, you might encounter errors related to Prisma's query engine binary not being found for your platform. This can happen if the Prisma Client was built on a different platform or if the correct binary target isn't specified. The error message may suggest adding a binaryTargets field to your schema.prisma, but with Wasp, you typically don't manage this file directly. This mismatch can cause the process to hang or fail without clear output.Wasp db studio not working? 3. Terminal/Process Issues: - If you run
wasp start db or similar commands, the terminal tab becomes occupied by the running process. You need to open a new terminal tab to run further commands. Sometimes, if you run commands in the wrong tab or directory, Wasp commands may appear unresponsive. Restarting the terminal and ensuring you're in the correct project directory can resolve this.
wasp db migrate-dev and wasp db studio not showing any output
4. General Troubleshooting Steps:
- Try running wasp clean to remove old build artifacts, then run your command again.
- Make sure you are in the correct project directory.
- If the terminal becomes unresponsive, close it, reopen, and navigate back to your project directory before running commands again.
If you have already installed Rosetta and are still experiencing issues, it may be related to the Prisma binary mismatch or a process/terminal issue as described above. If none of these solutions work, please provide more details or error messages for further assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @macevilc, 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?Ouch that sucks sorry! Can you confirm that
npm works correctly? For example running npm info npm should doWeirdly the problem doesn't occur anymore. It solved itself after a clean install. Thanks.
@macevilc I would blame npm for this, the registry is sometimes slow to respond in a specific region and just hangs the client forever. At any rate, glad to hear it's resolved!