feat(config): allow CoffeeScript configuration files

[eddiemonge]

Require CoffeeScript in the cli file to enable CS configuration and spec files. No other changes are needed to get CS files working. Possibly needs a readme or doc for the by issue but I haven't researched that much yet

Possibly fixes #38

[mary-poppins]

Thanks for the PR!

• Contributor signed CLA now or in the past
  • If you just signed, leave a comment here with your real name
• PR's commit messages follow the commit message format

If you need to make changes to your pull request, you can update the commit with git commit --amend.
Then, update the pull request with git push -f.

Thanks again for your help!

[juliemr]

I really don't want to introduce coffee script into Protractor's dependencies - the require can be done inside your config file, which seems like a cleaner solution. Maybe we can just document that option better instead?

[eddiemonge]

Then your config must be a JS file and not a CS file

[juliemr]

OK, I think the only thing opposing this is me being stubborn:

• coffeescript is not a large dep (412K)
• it's consistent with the way Karma includes coffeescript

So, merging.

[juliemr]

Merged as 7259614

[juliemr]

Quick note: spoke with Karma folks and updated to the following: 0257b5f

This allows the user to install coffee script but ignores failures if it's not present.

[andrewboni]

Is there an example somewhere of how to set up the protractorConf file (and specs for that matter) to use CoffeeScript? Just updated to Protractor 0.16.1, and am having trouble getting my JS specs to run with a protractorConf.coffee file.

[eddiemonge]

in your main project, you have to npm install --save coffee-script then it should start working like a champ. Thats after you checkout the project and npm link from inside the protractor directory since this change isn't pushed to npm yet.