Setting line endings to unix-style

[Pliavi]

DONE

• Add .gitattributes file that set all CRLF to LF (c299b99)
• Change the current CRLF files to LF
• Fix /usr/bin/env: ‘node\r’: No such file or directory #93

The project was written using DOS-style line endings (CRLF) that cause some problems when using the shebang notation as seen in #93 , it caused in the gitfolio 'bin' shebang that append \r to node binary name and the Unix systems can't find it.

One of the best alternatives is to convert the source files to Unix-Style (LF).

More about: https://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/

[imfunniee]

what about windows?

[Pliavi]

I'm looking forward about this, but I always end in an issue about without a concrete answer.
LF endings doesn't look to be a problem in windows, and as the problem occur only because of the shebang notation and not because of Javascript it may run without problems cause Windows ignore it.

Buuuut...
In a lot of these issues people say assume LF as default isn't a good ideia (but I dunno why)
The Git converts CRLF to LF when commit and do the inverse when checkout (so the line endings in the repo should be in LF anyway, something is already wrong here), but I'm not sure about NPM and Yarn, it look like that they have a different behavior, even when the @utkarshmani1997 in #93 experienced the same in both.

Thank you to keep this open, and i'll keep searching about to get the answer from good sources and a better way to solve this ^^

[Pliavi]

Some news about, you can merge it without problems, I tried where and git on windows converts LF to CRLF on clone.
And it will not cause any problems to Windows users, and will resolve to Linux one's and Mac (Unix) too, if it behave the same way as Linux.

Maybe the problem with pushing as windows CRLF was in your git installation, as default it is recommended to be "checkout windows-style, commit unix-style"

You would be using the last option, and commited with CRLF.

And as said in Github help (you can use the steps to fix your autocrlf config too), use a .gitattributes to make all commits in LF makes it be in a good way to share de development between any environment, without being afraid of line ending problems when people change or mess with the "autocrlf" behavior, this file will force them to keep commiting in LF style to avoid future problems as this one in #93 .

For this PR I did what was said in GitHub Help.