Tools: Build time for complete apps?

[LostInBrittany]

I've used polymer-cli to create a PWA version of a dashboard app that I'd built with Polymer (using pages.js as router...). I've begun from scratch, and imported only the components needed for the new app, using the app- elements when possible (router, par exemple).

Everything is great, except the building phase, that takes more than 5 minutes !

In the old app I used vulcanize as build tool, it wasn't quick but it was way faster than that, more or less one minute.

Is such a slow build time normal?

[justinfagnani]

It's a little slow right now, but we haven't seen 5 minutes, usually on the order of a few seconds.

We know that we run the analyzer and vulcanize multiple times during the bundling phase. This should scale with the number of fragments. Hw many fragments do you have? Do you see the same long times with just an entrypoint?

[CTOJoe]

We also have tried switching from vulcanize to polymer cli and are experiencing build times of over 5 minutes. This is also on pretty performant machines. Could build time essentially be cut in half if there was a flag to compile just bundled or unbundled?

[justinfagnani]

Even half the time at 2.5 minutes is far too long. I'd like to figure out what it is about the project or environment that's causing such long builds. Could we see some package.json dependency sections and maybe we can reproduce ourselves?

[LostInBrittany]

That works be great, right now I have no use for the unbundled, I'd really
like the flag 😊
On Jun 9, 2016 10:47 PM, "Joe Burger" [email protected] wrote:

We also have tried switching from vulcanize to polymer cli and are
experiencing build times of over 5 minutes. This is also on pretty
performant machines. Could build time essentially be cut in half if there
was a flag to compile just bundled or unbundled?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Polymer/polymer-cli/issues/254#issuecomment-225021504,
or mute the thread
https://github.com/notifications/unsubscribe/AAsVzBiNZLIIwaR7hisPKNqY9QX_oFGxks5qKHv4gaJpZM4Ix1F9
.

[LostInBrittany]

I can send you a bower.json and a package.json tomorrow, if it can help.
On Jun 10, 2016 7:06 PM, "Justin Fagnani" [email protected] wrote:

Even half the time at 2.5 minutes is far too long. I'd like to figure out
what it is about the project or environment that's causing such long
builds. Could we see some package.json dependency sections and maybe we can
reproduce ourselves?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Polymer/polymer-cli/issues/254#issuecomment-225239549,
or mute the thread
https://github.com/notifications/unsubscribe/AAsVzFZZy3x8x5qBYYp9fmlaagV8hwfSks5qKZmGgaJpZM4Ix1F9
.

[marcushellberg]

I have an app that was initially built with PSK that I'm now migrating to use Polymer CLI.

With the PSK gulp build target, a full build too 18s, of which 16s was vulcanize. With polymer build the bundled build takes 2.5minutes+ (it crashes at that point).

It seems like it's trying to uglify and include everything in the bower_components folder, including demos and tests for each dependency, which certainly brings up the build time.

On a related note: if I include polymerelements/paper-elements and iron-elements instead of the individual elements, does it increase the build time or bundle size? I know that with PSK and vulcanize, it would only include the actual components that had been imported in the bundle.

[LostInBrittany]

I've just updated to the last build of polymer-cli and the same build that took 5 minutes takes instead 2 minutes. And that's great !!!
Still slower than vulcanize but really great!!!

[FredKSchott]

Closed by #310