That does indeed fix it! I guess that means I should push for gulp-vulcanize to update its dependent version.
Thanks for the help, Eric. You rock. On Tuesday, January 6, 2015 3:31:20 PM UTC-5, Eric Bidelman wrote: > > Gulp vulcanize is using vulcanize 0.7.1 The latest vulcanize is 0.7.5 Can > you try running the latest version directly and see if that makes a > difference? > > On Tue, Jan 6, 2015 at 10:50 AM, Andrew Fallows <[email protected] > <javascript:>> wrote: > >> I was using gulp-vulcanize to execute the inlining; with both inline and >> strip turned on. >> >> I turned off both options so I could more easily check if polymer >> appeared more than once. It doesn't appear to -- with inlining disabled, I >> get *one* instance of >> >> <script src="assets/polymer/polymer.js"></script> >> >> My full gulp task is below >> >> module.exports = function(gulp, paths, helpers) { >> gulp.task('vulcanize', function() { >> var dest = './public'; >> var viewFile = './app/views/polymer/index.html'; >> var publicFile = './public/assets/index.html'; >> >> fs.createReadStream(viewFile).pipe(fs.createWriteStream(publicFile)); >> >> return gulp.src(publicFile) >> .pipe(vulcanize({ >> dest: dest, >> inline: false, >> strip: false >> })) >> .pipe(gulp.dest(dest)); >> }); >> }; >> >> >> On Tue Jan 06 2015 at 1:43:27 PM Eric Bidelman <[email protected] >> <javascript:>> wrote: >> >>> What is the vulcanize command you're running? >>> >>> To check if polymer.js is being loaded more than once, open the >>> vulcanized output and check for "polymer.js" or the inlined file (if you're >>> running --inline). >>> >>> On Tue, Jan 6, 2015 at 10:30 AM, Andrew Fallows <[email protected] >>> <javascript:>> wrote: >>> >>>> After looking at a few threads here and a few issues on the Polymer >>>> GitHub repo, it looks like getting an error of >>>> >>>> Uncaught HierarchyRequestError: Failed to execute 'appendChild' on >>>> 'Node': Nodes of type 'HTML' may not be inserted inside nodes of type >>>> '#document'. >>>> >>>> after vulcanizing a polymer application is usually a sign that >>>> polymer.js is getting sourced more than once. However, I'm having a hard >>>> time figuring out whether that's true for my project. >>>> >>>> I'm working on a project which uses a lot of custom components, and has >>>> a pretty long import hierarchy: >>>> >>>> >>>> - *foo-app* >>>> - *foo-header* >>>> - *foo-page-one* >>>> - *foo-hero-unit* >>>> - *foo-table* >>>> - *foo-page-two* >>>> - *foo-hero-unit* >>>> - *foo-slideshow* >>>> - *foo-footer* >>>> >>>> Each of these components imports polymer with a <link rel="import" >>>> href="../polymer/polymer.html"> -- however, vulcanize appears to be >>>> successfully eliminating multiple import (foo-hero-unit doesn't get >>>> imported twice), so I would expect polymer to only get imported once. I'm >>>> not sure how to confirm whether it is. >>>> >>>> What should my next debugging steps be? I'm happy to provide more >>>> information, too, but since this is a closed source application, that does >>>> have some unfortunate limitations. >>>> >>>> The full HTML of the file I'm vulcanizing is below. >>>> >>>> Thanks, >>>> Andrew Fallows >>>> >>>> <!doctype html> >>>> <html> >>>> <head> >>>> >>>> <meta >>>> name="viewport" >>>> content="width=device-width, minimum-scale=1.0, >>>> initial-scale=1.0, user-scalable=yes"> >>>> <title>Project Foo</title> >>>> <link rel="stylesheet" href="../assets/foo/base.css"> >>>> <script src="../assets/webcomponentsjs/webcomponents.js"></script> >>>> <link rel="import" href="../assets/foo-app/foo-app.html"> >>>> >>>> </head> >>>> >>>> <body unresolved> >>>> <foo-app></foo-app> >>>> </body> >>>> </html> >>>> >>>> Follow Polymer on Google+: plus.google.com/107187849809354688692 >>>> --- >>>> >>> You received this message because you are subscribed to the Google >>>> Groups "Polymer" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected] <javascript:>. >>> >>> >>>> To view this discussion on the web visit https://groups.google.com/d/ >>>> msgid/polymer-dev/9f8ecff0-5855-41eb-bea3-25f646b376a5% >>>> 40googlegroups.com >>>> <https://groups.google.com/d/msgid/polymer-dev/9f8ecff0-5855-41eb-bea3-25f646b376a5%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/910d1413-f4ec-4a11-9f22-e808185dd8fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
