Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why calling polymer.js instead of polymer.min.js? #1213

Closed
oswaldofreitas opened this issue Feb 23, 2015 · 4 comments
Closed

Why calling polymer.js instead of polymer.min.js? #1213

oswaldofreitas opened this issue Feb 23, 2015 · 4 comments

Comments

@oswaldofreitas
Copy link

captura de tela 2015-02-23 as 08 26 47

@ghost
Copy link

ghost commented Feb 23, 2015

I'm guessing it's because your pre-vulcanized source is <link>ing to polymer.html, which itself is <script>ing to polymer.js. Vulcanize should probably special-case processing polymer.html but doesn't seem to at the moment. As a quick workaround, just make your own polymer.html file that <script>s in polymer.min.js; the original is only two lines long.

@oswaldofreitas
Copy link
Author

It worked as a workaround, thanks. Would be nice if someone fix it ;)
I believe something like gulp-uglify is missing as a build task after vulcanize in generator-polymer...

@ebidel
Copy link
Contributor

ebidel commented Feb 23, 2015

For production, you should switch polymer.html over to use polymer.min.js. Alternatively, you can vulcanize your imports so this happens automagically.

@robdodson
Copy link
Contributor

@oswaldomilet I believe you can fix this by adding the inline: true option to the gulp task that runs vulcanize in the generator.

Moving issue over there: yeoman/generator-polymer#151

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants