Wasp start
Hi everyone,
I am trying to use Wasp for the first time and although I was able to get all the dependencies and code, I can't seem to be able to run. This is that I get when I do from my mac. I'd appreciate any help
MyApp % wasp start
🐝 --- Starting compilation and setup phase. Hold tight... ------------------------
🐝 --- Compiling wasp project... --------------------------------------------------
[ Wasp ] Starting npm install
[ Wasp !] npm ERR! code EACCES
[ Wasp !] npm ERR! syscall mkdir
[ Wasp !] npm ERR! path /Users/yllenfernandez/MyApp/node_modules/vite-node/node_modules/@esbuild/android-arm
[ Wasp !] npm ERR! errno -13
[ Wasp !] npm ERR! Error: EACCES: permission denied, mkdir '/Users/yllenfernandez/MyApp/node_modules/vite-node/node_modules/@esbuild/android-arm'
[ Wasp !] npm ERR! [Error: EACCES: permission denied, mkdir '/Users/yllenfernandez/MyApp/node_modules/vite-node/node_modules/@esbuild/android-arm'] {
[ Wasp !] npm ERR! errno: -13,
[ Wasp !] npm ERR! code: 'EACCES',
[ Wasp !] npm ERR! syscall: 'mkdir',
kely you do not have the permissions to access this file as the current user
[ Wasp !] npm ERR!
[ Wasp !] npm ERR! If you believe this might be a permissions issue, please double-check the
[ Wasp !] npm ERR! permissions of the file and its containing directories, or try running
[ Wasp !] npm ERR! the command again as root/Administrator.
[ Wasp !]
[ Wasp !] npm ERR! A complete log of this run can be found in: /Users/yllenfernandez/.npm/_logs/2024-03-15T22_56_49_043Z-debug-0.log
❌ --- [Error] Your wasp project failed to compile: -------------------------------
- npm install failed: Project setup failed with exit code 243.
❌ --- [Error] Compilation of wasp project failed: --------------------------------
1 errors found
5 Replies
Hi Yllen, you could try
sudo chown -R $(whoami) /Users/yllenfernandez/MyApp to make your user the owner.
Before you run that you can check current ownership using:
Thank you very much, I'll try that
Hey @Y. Fernandez, I second what @JR said- this looks like an file ownership issue, not related to Wasp.
Let m eknow if JR's suggestion worked (thanks for helping out @JR).
Do you have any kind of unique setup on your Mac @Y. Fernandez ? By default, you shouldn't be getting this issue -> maybe you have a bit unique setup regarding user permissions? Or any other uniqueness to your setup?
Not that I know. I'll try the commands suggested above. And thanks for replying @Filip