chore: decaffinate more test scripts

[realityking]

🚀 Why this change?

Removing some more cofffeescript bits & pieces.

Main advantage is that eslint lints these new JS files while nothing was linting the coffeescript files.

📝 Related issues and Pull Requests

This completes the work started in #992

✅ What didn't I forget?

• To write docs
• To write tests
• To put Conventional Changelog prefixes in front of all my commits and run npm run lint

[realityking]

Why would it work on Linux but fail on Windows? 🤔

[honzajavorek]

I didnt see the failing test (on mobile phone), but let me guess it’s the flaky beast we are trying to tame for second time in #1069

[realityking]

I don't think that's it. There are actually 32 failures, by the looks of it in places I've touched in this PR.

[michalholasek]

I wonder if coffee is doing file path delimiter normalization (\ vs. /). Might be worth it to try path.normalize or path.join.

[honzajavorek]

Hmm, interesting. Looking at the failures I can't exactly say what could happen. The code seems to be the same. I suspected some implicit returns missing, I couldn't spot something right away tho, or Windows not being able to find node in PATH. But from the last error it's obvious the server process got started, so node is fine.

[realityking]

It looks like most of the failures (all but one) are related in child-process-test.js which invokes the scripts differently (it's the only using spawn). I'll back out the things that are failing and make another PR for those.

[realityking]

A lot smaller in scope but at least the tests pass for what's in here :)

[michalholasek]

@realityking I am sorry for the delay, we've had quite a lot of other work on our plates. Thank you for the PR, it's great!

[realityking]

@michalholasek no worries, I know what it's like 🙂