A library of Gulp build tasks
polymer-build is a library for building Polymer projects.
npm install --save-dev polymer-build
The Polymer CLI uses polymer-build under the hood, so you can think of the CLI's
build command like running a pre-configured polymer-build pipeline. Setting this up for you makes the CLI easy to use, but as a command-line wrapper its customization options are more limited. polymer-build allows you to completely customize your build and combine additional streams and build tasks in any order.
Consider using polymer-build instead of the CLI if you:
While polymer-build was built to work easily with Gulp, it can be used in any Node.js environment. polymer-build is built on Node.js streams, and the build pipeline that you create with it is not much more than a series of connected streams. Files are represented as Vinyl file objects, which means that polymer-build can interop with any existing Gulp/Vinyl streams.
Check out the custom-build generator for an example of how polymer-build can be used to build a project.
PolymerProject represents your project in the build pipeline. Once configured, it will give you access to a collection of streams and helpers for building your project.
To create a new instance of PolymerProject, you'll need to give it some information about your project. See the
ProjectOptions definition for a full list of all supported options.
const project =entrypoint: 'index.html'shell: 'src/my-app.html'fragments:'src/my-view1.html''src/my-view2.html''src/my-view3.html';
NOTE: If you've previously used the Polymer CLI to build your project, these options are the same information that's held in your project's
polymer.jsonfile. If you prefer, you can continue to store these values in that file and then load them here.
const project = new PolymerProject(require('./polymer.json'));
#### project.sources()Returns a readable stream of your project's source files. By default, these are the files in your project's `src/` directory, but if you have additional source files this can be configured via the `sourceGlobs` property in [`ProjectOptions`](src/polymer-project.ts).#### project.dependencies()Returns a readable stream of your project's dependencies. This stream is automatically populated based on the files loaded inside of your project. You can include additional dependencies via the `includeDependencies` property in [`ProjectOptions`](src/polymer-project.ts) (this can be useful when the analyzer fails to detect a necessary dependency.)#### project.analyzerA stream that analyzes your project as files pass through it. Files pass through it untouched (although they may exit in a different order than they entered). The analyzer enables a lot of the more powerful features of polymer-build, like smart dependency analysis & bundling.**polymer.analyzer is a required step in your build-pipeline!** Be sure to pipe all files through it before piping out to your build destination(s). If dependencies aren't piped to `project.analyzer` the analyzer will hang.```jsconst gulp = require('gulp');const mergeStream = require('merge-stream');// pipe both streamsmergeStream(project.sources(), project.dependencies()).pipe(project.analyzer).pipe(gulp.dest('build/'));
A stream that combines the files in your application to reduce the number of frontend requests needed. This can be a great way to improve performance when HTTP2/Push is not available.
By default, the bundler will create one "shared-bundle.html" containing all shared dependencies. You can optimize even further by defining "fragments" in your project options. Fragments are lazy loaded parts of the application, typically views and other elements loaded on-demand. When fragments are defined, the bundler is able to create smaller bundles containing code that is only required for specific fragments.
const gulp = ;const mergeStream = ;// pipe both streams;
project.splitHtml() returns a stream that extracts any inlined CSS & JS into individual files. This can be useful for running your files through additional tools that don't handle inline code very well.
Note that this should be a temporary part of your overall build pipeline. Split files should always be rejoined with
project.rejoinHtml() as soon as possible in the pipeline.
const gulpif = ;const uglify = ;const cssSlam = gulp;const htmlMinifier = ;const mergeStream = ;const sourcesStream = polymerProject;// not shown: project.dependencies() can also be split & optimized;
generateServiceWorker() will generate the service worker code based on your build. Unlike other parts of polymer-build,
generateServiceWorker() returns a promise and not a stream. It can only be run after your build has finished writing to disk, so that it is able to analyze the entire build as it exists.
generateServiceWorker() is built on top of the sw-precache library. Any options it supports can be passed directly to that library via the
For bundled builds, be sure to set the bundled option to
true. See AddServiceWorkerOptions for a list of all supported options.
const generateServiceWorker = generateServiceWorker;
generateServiceWorker(), but writes the generated service worker to the file path you specify in the
serviceWorkerPath option ("service-worker.js" by default).
const addServiceWorker = addServiceWorker;
Sometimes you'll want to pipe a build to multiple destinations.
forkStream() creates a new stream that copies the original stream, cloning all files that pass through it.
const mergeStream = ;const forkStream = forkStream;const buildStream =;const unbundledBuildStream =;const bundledBuildStream =;
git checkout -b my-new-feature
git commit -am 'Add some feature'
git push origin my-new-feature
You can compile polymer-build from source by cloning the repo and then running
npm run build. Make sure you have already run
npm install before compiling.
polymer-build officially supports the latest LTS (4.x) and stable (6.x) versions of Node.js.