turbowatch icon indicating copy to clipboard operation
turbowatch copied to clipboard

Doesn't work on Windows

Open GeorgeTailor opened this issue 2 years ago • 1 comments

Expected Behavior

it actually runs

Current Behavior

fails with error:

> turbowatch ./turbowatch.ts

[turbowatch] running turbowatch without logging enabled; set ROARR_LOG=true to enable logging. Install @roarr/cli to pretty-print logs.
b6a6d891 > Set-Variable : A parameter cannot be found that matches parameter name 'euo'.
b6a6d891 > At line:1 char:5
b6a6d891 > + set -euo pipefail; export PATH="my_path\node_mo ...
b6a6d891 > +     ~~~~
b6a6d891 >     + CategoryInfo          : InvalidArgument: (:) [Set-Variable], ParameterBindingException
b6a6d891 >     + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.SetVariableCommand
b6a6d891 > export : The term 'export' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
b6a6d891 > At line:1 char:20
b6a6d891 > + set -euo pipefail; export PATH="my_path\node_mo ...
b6a6d891 > +                    ~~~~~~
b6a6d891 >     + CategoryInfo          : ObjectNotFound: (export:String) [], CommandNotFoundException
b6a6d891 >     + FullyQualifiedErrorId : CommandNotFoundException
b6a6d891 >

Possible Solution

Steps to Reproduce

  1. use on Windows machine

Logs

GeorgeTailor avatar Apr 07 '23 14:04 GeorgeTailor

I am not a windows user and have no exposure to windows platforms.

If there was a contributor that got it to work on Windows, then I'd be happy to add windows platform to the test suite to ensure future compatibility.

Will leave this issue open if Windows fan emerges that wishes to make Turbowatch work with Windows.

gajus avatar Apr 10 '23 17:04 gajus