windows support

[james-elicx]

Reports from various people/channels that Windows has issues.

• figure out (investigate) what the problem areas are
• fix issues that come up
• update docs where applicable

[dario-piotrowicz]

The opennextjs-aws code we rely on already doesn't seem to fully support windows, at least according to this warning.

@conico974 do you have more context/info to provide regarding that? do you know what makes the aws adapter not windows-compatible (is there anything specific, some general issue, etc...)?

[conico974]

Honestly i haven't touched windows at all for OpenNext, but i knew of a few issues

• Next itself used to have issues when built in windows but deployed in linux.
• There are issues with libs that use native code (if i'm not mistaken, it's because of file tracing)
• There used to be some issues in OpenNext itself, but they should be fixed (or at least the necessary fix should be similar) [windows] Specify the file:// protocol when importing config on Windows opennextjs-aws#460 [windows] Add Windows compatibility for the resolve ESBuild plugin opennextjs-aws#461 [windows] Add Windows compatibility for the replacement ESBuild plugin opennextjs-aws#465

It should work now, but since i haven't worked on this we just kept the warning

[james-elicx]

Thanks for the PR links. Fully enough, I actually had one of them open already :)

Had to update some of the esbuild filters in opennextjs/opennextjs-aws#695 as you suspected. There were a couple of paths that needed normalizing on our side as well.

[dario-piotrowicz]

Thanks a bunch @conico974 for the info (sorry for the late reply I only now noticed your comment), I see, the situation is kinda like I suspected (Next not being fully there and us not testing/investing into it).

I'd personally be fine keeping the warning although I think it could be great if we could maybe document this more, at least for visibility/transparency (basically something like your comment but in a docs format)