This template offers a starting point, based upon Polymer App Toolbox - Starter Kit (PSK V2). Implementing Polymer-Redux, the PRPL pattern and Babel for ES2015 transpilation.

This command serves the app at http://localhost:8080 and provides basic URL routing for the app, in accordance with PSK V2:

npm start

This command performs a build of the app via Gulp, beginning with a Babel transpliation. Following this, the standard polymer-cli build runs which performs the below.

Polymer-CLI build runs a HTML, CSS, and JS minification on the application dependencies, and generates a service-worker.js file with code to pre-cache the dependencies based on the entrypoint and fragments specified in polymer.json. The minified files are output to the build/unbundled folder, and are suitable for serving from a HTTP/2+Push compatible server.

In addition the command also creates a fallback build/bundled folder, generated using fragment bundling, suitable for serving from non H2/push-compatible servers or to clients that do not support H2/Push.

npm run build

This command removes all existing build and temporary files:

npm run clean

This command will run Web Component Tester against the browsers currently installed on your machine and also run linting.

Note: The testing and will run POST Babel transpilation:

npm test

You can extend the app by adding more views that will be demand-loaded e.g. based on the route, or to progressively render non-critical sections of the application. Each new demand-loaded fragment should be added to the list of fragments in the included polymer.json file. This will ensure those components and their dependencies are added to the list of pre-cached components and will be included in the bundled build.

The PRPL pattern, in a nutshell:

• Push components required for the initial route
• Render initial route ASAP
• Pre-cache components for remaining routes
• Lazy-load and progressively upgrade next routes on-demand