`wasp start` failing on windows

[Martinsos]

Wasp doesn't yet have native support for Windows, explained here: #47 (comment) .

But, you can use it nicely via WSL (Windows Subsystem for Linux)!

Once you set up Ubuntu on WSL, just follow Linux instructions for installing Wasp. If you need further help, reach out to us on Discord - we have some community members using WSL that might be able to help you.

Note: If you are using WSL2, make sure that your Wasp project is not on Windows file system, but instead on Linux file system. Otherwise, Wasp won't be able to detect file changes, due to the issue in WSL2.

[abelsgowah]

So the app can't be run on window?

[infomiho]

You can develop the app on Windows easily using the Windows Subsystem for Linux. It's a feature of Windows that enables you to use Ubuntu/any other Linux, quite easily and it's the preferred way of many to develop on Windows. The best intro we have for this topic is here: https://wasp-lang.dev/blog/2023/11/21/guide-windows-development-wasp-wsl

[nodtem66]

I suspect that Haskell's System.Process proc can't identify the executable called npm because it is npm.ps1 in Windows:

>Get-Command npm
CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
ExternalScript  npm.ps1                                                       C:\Program Files\nodejs\npm.ps1

as well as npx.

> Get-Command npx
CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
ExternalScript  npx.ps1                                                       C:\Program Files\nodejs\npx.ps1

I'm trying to patch it with System.Process shell. I'll update this later once I have a progress with this.