-
Notifications
You must be signed in to change notification settings - Fork 23
Uncaught EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an al... #104
Comments
+1 |
Published an update that includes an update of |
I'm still seeing the error with 0.11.0 😐 I can help debug if you can point me in the right direction. |
From this part of the stack trace:
It looks like |
@Arcanemagus Any updates on this? Have you reached out to @jkillian et al about this if it is indeed an issue with tslint proper? |
I'm not aware of any places where we're doing any |
I found this problem as well trying to use tslint@next / typescript@next for my project and did some debugging. EDIT: I tried replacing |
Strange, maybe worth filing an issue on TypeScript and seeing if they have any input? |
I've traced to issue to this PR in the Typescript repo (microsoft/TypeScript#9580) that's causing the |
I still see the error: linter-tslint: 0.11.1
|
@radarsu Please file a new issue with that stack trace. Also in that issue please answer whether |
npm init
npm install tslint@next typescript@next --save
Atom Version: 1.8.0
System: Mac OS X 10.11.5
Thrown From: linter-tslint package, v0.10.0
Stack Trace
Uncaught EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self'".
Commands
Config
Installed Packages
The text was updated successfully, but these errors were encountered: