It looks like JewelJS.swc includes some classes in the SWC that probably shouldn't be there. One example (but there are many more): org.apache.royale.states.State.
These are core classes that should be from dependencies, and I suspect that something might be on the library-path instead of the external-library-path. Because the compiler found the class in JewelJS.swc, it assumes that it needs defaults.css from JewelJS.swc too. To try to reproduce this issue, I created a sample app that uses only Basic components. I'm seeing that the compiler is trying to use defaults.css from Basic, Express, Jewel, and MaterialDesignLite. I'll take a look at the compiler options for some of the other SWCs to see if anything catches my eye. -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Tue, Jul 9, 2019 at 3:21 AM Harbs <[email protected]> wrote: > I have no jewel components in my app, but I’m suddenly seeing TONS of > jewel css in my app. > > Similarly, I’m seeing Basic CSS (such as Button) which did not used to be > included (and is messing up the visuals in my app). > > Has something changed with the logic which includes CSS? > > Harbs
