Use loophole package to to fix #104

[guncha]

Atom packages are running with Content Security Policy (CSP) set to disallow eval-like behavior. Recent change in Typescript (microsoft/TypeScript#9580) added code that uses new Function(...) which will cause linter-tslint package to fail to initialize with the error as seen in #104.

This PR uses package loophole (https://github.com/atom/loophole) created by the Atom team to specifically address issues like this. I've also commented on the above mentioned PR and will try to open an issue with the Typescript team. Meanwhile, this workaround restores functionality of linter-tslint when used with typescript@next.

[dsifford]

I'm running @guncha 's patch on my machine (64-bit Linux) and it seems to be working perfectly fine.

Nice work @guncha

[Arcanemagus]

Until TypeScript fixes this on their end, I guess workarounds like this are necessary. Merging and thanks!

[Arcanemagus]

Published in v0.11.1 🎉.