-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The "enableDiagnostics" option is broken in 22.4.0 #455
Closed
severen opened this issue
Feb 26, 2018
· 4 comments
· Fixed by #457 · May be fixed by baophucct/create-react-app-typescript#4
Closed
The "enableDiagnostics" option is broken in 22.4.0 #455
severen opened this issue
Feb 26, 2018
· 4 comments
· Fixed by #457 · May be fixed by baophucct/create-react-app-typescript#4
Comments
I think either reverting back the change to bring |
This is weird because it doesn't fail in tests. I'll take a closer look at this |
Hi, I'm facing the same issue here. Is there a way to work around this for the time being? |
This was referenced Mar 19, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In previous versions of ts-jest the enableDiagnostics option worked without issues. Starting with 22.4.0 it seems that some change in ts-jest's internal configuration has broken it.
I have confirmed with some local testing that disabling enableDiagnostics as is the default keeps ts-jest working.
A hopefully minimal enough repro and logs containing the relevant errors (check the Travis build error) can be found at this pull request on a project of mine.
The text was updated successfully, but these errors were encountered: