Should package.json scripts etc. accommodate Windows development?

[gibson042]

(originally posted by @boneskull in https://github.com/endojs/endo/pull/2821#discussion_r2103392181)

' in package scripts isn't portable to pwsh/cmd.

Ideally, contributors should be able to use a native Windows dev environment—but I'm under no illusions that is going to happen in the near future.

[boneskull]

On the one hand: this would enable Windows users to contribute. Improving the contributability of an OSS project is not a bad thing.

On the other: there are many bash scripts and (likely) places in the codebase where Endo doesn't consider the possibility of Windows-style paths.

Converting scripts (probably to JS, since it's there already) is a tall order. This would need to happen gradually.

I think we should ask (whether we have an answer or not):

1. Does Endo have any current contributors who use Windows that would rather not need to reach for WSL?
2. Does Endo have any users (current or prospective) who actually want to run Endo in production on a Windows machine?
3. How important is it for Endo's project health that it attract & retain new contributors?

I can't answer 1, 2 is probably "no", and I can only speculate at what others think about 3.

[boneskull]

@gibson042 Maybe this issue should be renamed to reflect that we're really talking about supporting Windows and thus talking about encouraging new contributions (by removing roadblocks to contribution). 🤷