Rename lib/babel.js to lib/test-worker.js

[ariporad]

See #374.

[sindresorhus]

Why change this file? Looks unrelated to the intent of this pull request.

[ariporad]

I didn't... I have absolutely no clue why that's there.

[sindresorhus]

Can you remove that change? And the below file change too.

[ariporad]

Ok @sindresorhus, that should be fixed now.

I have no clue why that happened... It looks like WebStorm automagically un-babel'd it.

[jamestalmage]

WebStorm asks you about adding a file watcher whenever it sees ES6 code. If you accidentally click yes, this can happen. I keep meaning to figure out where the setting is just to turn that off.

[ariporad]

No, I get that. But it appears that WebStorm un- babel'd the code. It's
very strange.
On Sat, Dec 26, 2015 at 9:46 PM James Talmage notifications@github.com
wrote:

WebStorm asks you about adding a file watcher whenever it sees ES6 code.
If you accidentally click yes, this can happen. I keep meaning to figure
out where the setting is just to turn that off.

—
Reply to this email directly or view it on GitHub
#375 (comment).

[vadimdemedes]

When I see child.js I am asking myself a question "child of what?". In my opinion, it is just as unclear as babel.js. How about forked-process.js, worker.js, test-worker.js?

[ariporad]

@vdemedes: what about "subprocess.js"?

[vadimdemedes]

@ariporad subprocess.js works too. Let's see what other guys think.

[jamestalmage]

test-file-launcher.js

[jamestalmage]

Also, please paint the bikeshed green.

[vadimdemedes]

@jamestalmage a bit long, I think.

[jamestalmage]

test-launcher.js or test-worker.js

[ariporad]

@jamestalmage, @vdemedes: I still like subprocess.js or child.js.

And the bikeshed is to be blue.

[vadimdemedes]

@jamestalmage++

[sindresorhus]

👍 test-worker.js

[ariporad]

Ok, I'll change it to test-worker and update the commit.