Chad Killingsworth
Chad Killingsworth
@ed-ilyin Looks like something is bringing in the wrong version of `iron-a11y-keys-behavior`. I know not all of the polymer elements are fully working in 3.0 yet.
With Polymer 3, you don't need a loader. If you want to post-process HTML, then you're code will look like: ```js import fooTemplate from './foo-element.html'; class FooElement extends Polymer.Element {...
Polymer 3 support added in #96
Can you get a minimal demo of this behavior built? Ideally adding another demo of this to the project. Then I can take a look.
I can fix the loading order, but that alone won't get the results you are after. Closure-compiler has an optimization called cross chunk code motion. It's purpose is to push...
Without the IIFE you pollute the global namespace. You can also end up with conflicts with other libraries.
Yes that would be would be a bug. The harder question is determining exactly why it is occurring. It most likely means that the dependency graph is wrong.
What's a good way to trigger this just so I can double check it does what it says?
Retriggering CI
In AGRESSIVE mode, all of the chunks are passed to the compiler in one single compilation. The dependency tree is normalized and relationships are clearly defined. In STANDARD mode, each...