Windows development
Windows runs node natively
Windows runs docker natively
What are the current challenges with installing Wasp-Lang in Windows without WSL?
2 Replies
Hi @Juan. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
While Windows can indeed run Node.js and Docker natively, there are still some challenges with installing and running Wasp directly on Windows without using WSL (Windows Subsystem for Linux). Here are the main issues:
1. Incomplete Windows support: According to the Wasp documentation (https://wasp-lang.dev/docs/quick-start#installation-1), Wasp is close to working on Windows, but there are still some bugs preventing it from fully functioning. The Wasp team is working on resolving these issues, but they're not completely solved yet.
2. File system compatibility: When using WSL2, there's a known issue where Wasp can't detect file changes if the project is on the Windows file system rather than the Linux file system. This suggests that there might be similar file system compatibility issues when trying to run Wasp natively on Windows Discord thread (https://discord.com/channels/686873244791210014/1213985542480597022).
3. Dependency on Linux-specific libraries: Wasp seems to have dependencies on certain Linux libraries. For example, there was an issue reported where Wasp required specific versions of GLIBC, which are Linux-specific libraries Github Issue (https://github.com/wasp-lang/wasp/issues/867). This indicates that Wasp might be relying on some Linux-specific components that aren't directly available on Windows.
4. Installation process: The current installation instructions for Wasp are primarily designed for Unix-like systems (Linux and macOS) or for use with WSL on Windows. There isn't a native Windows installer available yet Discord thread (https://discord.com/channels/686873244791210014/1205980916837523496).
5. Development focus: The Wasp team has prioritized WSL as the recommended way to use Wasp on Windows for now. This suggests that native Windows support, while planned, is not the current focus of development efforts Discord thread (https://discord.com/channels/686873244791210014/1205980916837523496).
Given these challenges, the Wasp team currently recommends using WSL for Windows users who want to work with Wasp. They have provided a guide for setting up Wasp with WSL (https://wasp-lang.dev/blog/2023/11/21/guide-windows-development-wasp-wsl) to help Windows users get started.
The Wasp team has mentioned that full native Windows support is planned and likely to happen in the future, but they haven't provided a specific timeline for when this will be available Discord thread (https://discord.com/channels/686873244791210014/1205980916837523496).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Juan, 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?
Thanks. This should be enough for me to read through