Results 28 comments of Ryan Zec

So the generated code looks like this in case it is useful to you (with 6.5.x version of babel): ``` javascript 'use strict';var _createClass = function () {function defineProperties(target, props)...

Still the same issue with that block of code relating to filesForCoverage removed. I mean since it just includes files it should not cause any issues (not to mention I...

It was the `import * as React` that was causing the issue. Weird that other locations use that way of importing did not report the same issues. I do agree...

Ok, getting this issue again. This seems to be an issue when using `import * as ...`, the new use case is: ![screen shot 2016-03-05 at 8 16 16 pm](https://cloud.githubusercontent.com/assets/444206/13551652/8a5415aa-e30f-11e5-9dba-b6747ede58c7.png)...

More weirdness in the results: ![screen shot 2016-03-06 at 6 33 24 am](https://cloud.githubusercontent.com/assets/444206/13553872/7bc26c0c-e365-11e5-918d-c219ed31cbe3.png) I am not sure why it is telling me that the red highlight statement is not covered...

I guess I will use the 1.x.x branch of the regular istanbul and see how using that goes.

@lukasoppermann Disabling modes would not fix my issue as I specifically need to account for all the modes. > as you would normally set modes outside and load the mode...

@lukasoppermann Does my use case make sense or am i missing something about the use of variables in Figma?

That is exactly what I am doing but in order to create those 2 files, I need all modes to be accounted for and since in Figma, I can and...