-
Notifications
You must be signed in to change notification settings - Fork 110
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
TS 2.2.1 broke everything! #92
Comments
Hey @jdanyow, I get the same error on my end with |
Ok, there are breaking changes, objects that were just a plain old object literal |
The new |
Ok, the build passes on Travis and AppVeyor now with Does the example project work for you if you install from the latest dev branch, All the examples have been moved into |
Using |
@erikbarke Just a suggestion - maybe you should rename the issue to something like "TS 2.2.1 broke everything!" to avoid duplicate reports in the future. |
@dnasir, done! |
|
@unlight, I'm hoping to release within a few weeks! |
Uncaught ReferenceError: exports is not defined (Just making sure this error message is searchable as suggested in #96) |
TS 2.2.1 and Karma-TypeScript@2.1.8 is still not working for me. |
3.0.0-beta.1 is on npm now with support for Typescript 2.2.1:
(2.1.8 ended up having so much new functionality + breaking changes it was renamed to 3.0.0) |
I'm getting a bunch of errors trying the beta, a few examples are included below:
Quite a bunch of these.
Some of these.
A lot of these. |
Hey @vidartf, that's weird, I'm only getting a lot of this error: I get this error on my laptop (OSX), on Travis (Ubuntu), Appveyor (Windows) but I haven't seen your errors, what OS are you on, npm version, node version, Typescript version etc? |
OS: Windows (10), |
I'm also seeing a lot of duplicate errors from |
Actually, the code I have is failing |
Fixed those issues with tsc, no change in karma-typescript behavior. |
Here is full log with debug (from a full project, not able to do a minimal example yet): https://gist.github.com/vidartf/29e7d3204207d0ac588f8cf108324025 |
Actually, all those errors are from going from karma-typescript 2.1.7 -> 3.0.0. I only saw them previously because 2.1.8 got installed. On TS 2.1 I see the same errors. Using 2.1.7 + TS 2.2.2 simply does not discover any tests ( |
@vidartf, I can't reproduce this... I've tried the latest from master, the latest beta from npm on Windows 10 and I just don't get these errors when running the integration tests. Could you create a minimal repro project please? KT2.1.7 doesn't work at all with typescript TS2.2.2, there were breaking changes in TS2.2.1. |
@erikbarke I narrowed the problem down. It seems that karma-typescript is messing up |
More specifically, it seems to be screwing up the directory to use as the base for those patterns (it should be the same directory as the file is in?). |
Extra note: Event without the |
@vidartf, nice detective work, this was really easy to reproduce using your example project! I'll try to come up with a fix before the 3.0.0 release tomorrow. |
@vidartf, I've committed a fix now, does it work if you try the latest from the master branch, |
A quick test seem to work nicely 👍 3.0 also has some more things fixed compared to older versions, so I could clean up some old workarounds! :) |
The updated readme text was also a nice touch 👍 |
@vidartf, awesome! This means 3.0.0 is ready for release 😄 |
The text was updated successfully, but these errors were encountered: