You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The BuildBundler transform stream sends everything through and then after it bundles, it sends the bundle files through, typically with the same name as the fragment.
In practice, this is not causing problems for people, because the subsequent bundled files wind up overwriting the previous ones in a typical gulp stream setup. But when this winds up causing problems it may be very confusing to our users to diagnose and correct.
For this reason, we need to stop the output of bundled filenames. The downside is that the naive fix will be to hold up all html files in the stream until after bundling, which creates a bottleneck, but fixing this will dovetail with a fix for https://github.com/Polymer/polymer-build/issues/70 anyways.
The text was updated successfully, but these errors were encountered:
The
BuildBundler
transform stream sends everything through and then after it bundles, it sends the bundle files through, typically with the same name as the fragment.Example:
In practice, this is not causing problems for people, because the subsequent bundled files wind up overwriting the previous ones in a typical gulp stream setup. But when this winds up causing problems it may be very confusing to our users to diagnose and correct.
For this reason, we need to stop the output of bundled filenames. The downside is that the naive fix will be to hold up all html files in the stream until after bundling, which creates a bottleneck, but fixing this will dovetail with a fix for https://github.com/Polymer/polymer-build/issues/70 anyways.
The text was updated successfully, but these errors were encountered: