Don't do scriptInHead by default

[robdodson]

If you use a tool like Babel with Crisper then the scriptInHead bit will cause all kinds of hard to debug race conditions. Because the option feels like a performance tuning thing, it seems like you'd want to make in opt-in for advanced users. cc @ebidel

[ebidel]

What sort of race conditions? Defer will load but not execute until the
parser is done.

On Tue, Mar 15, 2016, 5:08 PM Rob Dodson notifications@github.com wrote:

If you use a tool like Babel with Crisper then the scriptInHead bit will
cause all kinds of hard to debug race conditions. Because the option feels
like a performance tuning thing, it seems like you'd want to make in opt-in
for advanced users. cc @ebidel https://github.com/ebidel

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#35

[robdodson]

It's a bit easier to show by going through the ES2015 code lab. With the script tag moved outside of dom-module and placed at the head of the page with defer, elements start throwing ReferenceErrors saying Polymer is not defined.

It may be because only my elements are deferred, whereas all the Polymer elements continue to use their original structure. Really not sure. But to make ES2015 work with Crisper I think you have to do scriptInHead (unless maybe you're vulcanizing first and then crispering everything).