feature/eolfix: weyland build fails on Mac OS

Resolves issue #1. I read through the thread for #1 and also read a bunch of the proposed workarounds, but none of them were solutions to the actual issue. Somehow a file with CRLF got pushed to NPM during a package update. I strongly believe that an end user should not have to perform a hacky workaround and patch a file by changing it's line endings after installing it from a package registry. It's an authoring/publishing issue that needs to be settled correctly for cross platform open-source projects. 

At my work we have a hybrid environment of Mac and Windows. We've gone to the extent of using EditorConfig and putting together a fairly specific `.gitattributes` file. I've moved over a few things that I felt were relevant and generic as far as configuration settings.

I know that there is a lot of file changes in this pull request. This is mostly due to having all of the NPM packages committed to GitHub. I went ahead and removed `node_modules` folder from the repo and also excluded it from Git.

Overall I believe that I was able to squash out all of the EOL issues in all of the source files. @EisenbergEffect, if you install EditorConfig in you editor of choice you shouldn't run into this issue again when publishing to NPM.

### Summary of Changes ###

* Removes `node_modules` folder
  * All Node dependencies are managed by NPM and the `package.json` making the node_modules folder unnecessary for hosting in Git.
* Adds `.editorconfig` configuration file to help manage line endings, indention, and white space.
  * You will need to install plugin for your favorite [editor](http://editorconfig.org/#download) to make use of this.
* EOL change.
* Updates .gitattributes and .gitignore with more specific options to help manage line ending issues.
* Please follow the commands [here](https://help.github.com/articles/dealing-with-line-endings#re-normalizing-a-repository) for re-normalizing a repository.