Can I assume that any types in external swcs will not have this issue? > On Mar 29, 2017, at 8:11 AM, Alex Harui <aha...@adobe.com> wrote: > > > > On 3/28/17, 9:58 PM, "Harbs" <harbs.li...@gmail.com> wrote: > >> OK. Why is this happening now? > > In order to handle the reordering of dependencies, I needed to collect > types used in static initializers. The code is throwing a big net over > all sorts of identifiers. I suppose I need to make it smarter, not sure. > > But it could just be that NativeUtils should contain all of these JS > "types". Although I'm a bit surprised to see NaN in there. > > -Alex >
- Re: Falcon build failing Alex Harui
- Re: Falcon build failing Harbs
- Re: Falcon build failing Alex Harui
- Re: Falcon build failing Alex Harui
- Re: Falcon build failing Harbs
- Re: Falcon build failing piotrz
- Re: Falcon build failing Harbs
- Re: Falcon build failing Alex Harui
- Re: Falcon build failing Harbs
- Re: Falcon build failing Alex Harui
- Re: Falcon build failing Harbs
- Re: Falcon build failing Alex Harui
- Re: Falcon build failing Harbs
- Re: Falcon build failing Alex Harui
- Re: Falcon build failing piotrz
- Re: Falcon build failing Alex Harui
- Re: Falcon build failing piotrz
- Re: Falcon build failing Harbs
- Re: Falcon build failing Alex Harui
- Re: Falcon build failing Harbs
- Re: Falcon build failing Harbs