Appveyor result: https://ci.appveyor.com/project/Nilzor/composer/build/appveyor%204#L454

Down to 6 errors - all related to HtmlReportSpec.kt, which requires a lot more work to fix on Windows (Not linefeed-related)

@Nilzor regarding 6 issues with the HtmlReportSpec.kt - tests expect Nodejs is present and are supposed to work in Docker container with ci/build.sh, which contains all the needed environment for that.
I guess we'll need a separate script and container for running all on Windows (or is running Linux Docker images possible/not painful on Windows, I'm not sure really).

Do we really need to be able to run the tests on Windows though? Having the production code running on Windows and having the development environment run are two different things.

Running docker on Windows is definitely possible, I'm just not sure it's worth investing in it. There are a couple of approaches we could take:

• Create a Windows version of build.sh : build.ps1 or build.cmd (most amount of work).
• Document how to run Docker in Bash on Ubuntu for Windows and make any changes needed, if any (I haven't tried that approach yet - not sure if Docker will run in this environment)
• Document how to run Docker in Linux VM on Windows (Basically not supporting Windows as a unit testing enviornment)

I'm leaning towards number 3, or not doing anything at all with regards to testing on Windows

PS: Thanks for the merge - could you also please make a new release build?

Well, running all tests on Windows would make us sure that all stuff continues working on Windows after new changes.
Let's stick with option 3 for now, ideally considering 1 one somewhere in future)

Pushed new release, too.