fix(configParser): load coffee and typescript for child processes

Without loading coffee in configParser.js, child processes which
try and load a coffeescript config file do not have coffee
registered with node's required, and child tests fail.

Fixes an issue with using coffeescript config files.

Author: Nick Radford

lib/cli.js

@@ -6,22 +6,6 @@
  */
 'use strict';
 
-// Coffee is required here to enable config files written in coffee-script.
-// It's not directly used in this file, and not required.
-try {
-  require('coffee-script').register();
-} catch (e) {
-  // Intentionally blank - ignore if coffee-script is not available.
-}
-
-// LiveScript is required here to enable config files written in LiveScript.
-// It's not directly used in this file, and not required.
-try {
-  require('LiveScript');
-} catch (e) {
-  // Intentionally blank - ignore if LiveScript is not available.
-}
-
 var util = require('util');
 var path = require('path');
 var child = require('child_process');

lib/configParser.js

@@ -3,6 +3,19 @@ var path = require('path'),
     util = require('util'),
     protractor = require('./protractor.js');
 
+// Coffee is required here to enable config files written in coffee-script.
+try {
+  require('coffee-script').register();
+} catch (e) {
+  // Intentionally blank - ignore if coffee-script is not available.
+}
+
+// LiveScript is required here to enable config files written in LiveScript.
+try {
+  require('LiveScript');
+} catch (e) {
+  // Intentionally blank - ignore if LiveScript is not available.
+}
 
 module.exports = ConfigParser = function() {
   // Default configuration.