[Feature] support windows OS for development

[vicb]

Windows OS is not fully tested / probably broken for development.

We plan to support windows as best as we can (some packages might not be compatible) as a development platform. For deployments, we will recomment using Linux/Mac (i.e. Workers Build).

[vicb]

Unfortunately we will not be able to support Windows without using WSL.

The reason is that next build does not work on windows (it would succeed on the first run and fails on the second run).

We will publish docs on how to use WSL on windows to be able to use it as a dev platform.

[Hades32]

The official NextJS build definitely works on Windows. What exactly is the issue you're seeing?

[vicb]

Building i.e. the playground14 example in standalone mode ({"output": "standalone"} in the next config which is what Open Next uses even if not specified explicitly) twice fails the second time.

[vicb]

@Hades32 Returning the question: what problem do you see with using WSL?

[Hades32]

Primarily the IDE support is much worse, basically requiring remote development, which mostly works in vscode but is still really bad in JetBrains'. Especially an issue when your npm dependencies differ between OSs. Also WSL uses quite a bit of extra memory and is just not as fast as working fully natively.

It's great tech and fantastic for projects that really can't support Windows, but should really be a last resort

[vicb]

Given that Next.js itself doesn't fully support windows, we are not going to invest more time on that topic.

Note that both Next.js and OpenNext are open-source projects and we will gladly accept PRs.

Updated the doc in opennextjs/docs#141