Getting EISDIR errors when trying to run Wasp
When trying to perform either "wasp start" or "wasp db migrate-dev", during the npm install section, i get an EISDIR when it tries to create a symlink from .wasp/out/sdk/wasp to app/node_modules.
I tried creating the symlink myself beforehand, but it then just hits EISDIR when trying to lstat that same file .
Wasp version is 0.15.2
Platform is WSL
6 Replies
Hi @whiskers. 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 provided in the knowledge sources, it appears that you're encountering an issue related to running Wasp on Windows using WSL (Windows Subsystem for Linux). This is likely due to file system incompatibilities between Windows and WSL. Here's what you need to know:
1. WSL2 File System Issue: There's a known issue with WSL2 where file changes are not properly detected when the project is on the Windows file system. This can cause various problems, including the EISDIR errors you're experiencing Github Issue #603 (https://github.com/wasp-lang/wasp/issues/603).
2. Solution - Move to Linux File System: The recommended workaround is to move your Wasp project to the Linux file system within WSL. This should resolve the file detection issues and allow Wasp to function correctly Discord Support Thread (https://discord.com/channels/686873244791210014/1213985542480597022).
3. WSL Setup Guide: Wasp provides a detailed guide for setting up and using Wasp with WSL. Following this guide should help you avoid these issues Wasp Blog - WSL Guide (https://wasp-lang.dev/blog/2023/11/21/guide-windows-development-wasp-wsl).
To resolve your specific issue:
1. Ensure your Wasp project is located on the Linux file system within WSL, not on the Windows file system.
2. Delete the
.wasp folder in your project directory.
3. Try running wasp start or wasp db migrate-dev again.
If you continue to experience issues after following these steps, you may want to consult the Wasp documentation or reach out to the Wasp community on Discord for further assistance.
Remember, when using WSL2, it's crucial to keep your Wasp projects on the Linux file system to avoid file detection and permission issues Wasp Docs - Quick Start (https://wasp-lang.dev/docs/quick-start#installation-1).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @whiskers, 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?@whiskers this is likely related to the fact it is running on WSL hm! Have you ensured your proejct is on Linux file system, not Windows?
@Filip any thoughts? Seems that thishappens while we tryto create a symlink to wasp sdk, because operation is illegal on a directory -> you will probably have an idea about this?
As far as I can tell, it's in the linux file system. The file in questions is: \wsl.localhost\Ubuntu\home\whiskers\story\app.wasp\out\sdk\wasp
For anyone else with this issue, I started over, but this time didn't use apt to install node, only nvm. (Found a post mentioning this) and it seemed to do the trick.
This microsoft page: https://learn.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-wsl
Set up Node.js on WSL 2
A guide to help you get your Node.js development environment set up on Windows Subsystem for Linux (WSL).
Which i found due to this post (as when I created the symlink manually, I was just finding more EISDIRs from lstats) https://stackoverflow.com/questions/76263708/npm-err-path-wsl-localhost-ubuntu-22-04-home-jdoe-devprojects-litenotes-node
Stack Overflow
npm ERR! path \wsl.localhost\Ubuntu-22.04\home\jdoe\DevProjects\li...
Presently, I am attempting to create a PHP laravel app and install some nodejs dependencies on wsl-2 but am getting the following errors (cf. https://www.linkedin.com/learning/laravel-9-0-essential-
Oh wow ok didn't expect this to be a solution but great to hear it worked!