A starting point for Polymer apps
Go to file
Abdón Rodríguez Davila d8ec3b8ed4 Merge branch '3.0-preview' into 3.0-preview-update
# Conflicts:
#	.travis.yml
2018-04-27 20:30:08 +02:00
.github Fix #1015 2017-06-01 19:26:27 +02:00
images Merge in app-drawer-migration 2016-08-22 12:14:42 -07:00
src Use single quotes 2018-04-26 21:42:56 +02:00
test Revert date changes in license comments. 2018-04-19 18:33:20 -07:00
.gitattributes Update Travis setup as Polymer/polymer 2018-04-21 13:12:54 +02:00
.gitignore Update to 3.0 pre-release toolling 2018-04-16 15:01:53 -07:00
.travis.yml Merge branch '3.0-preview' into 3.0-preview-update 2018-04-27 20:30:08 +02:00
index.html Remove last ESLint presence 2018-04-21 13:12:54 +02:00
manifest.json Update manifest.json 2017-10-02 12:40:29 -07:00
package-lock.json v4.0.0-pre.2 2018-04-20 18:04:07 -07:00
package.json v4.0.0-pre.2 2018-04-20 18:04:07 -07:00
polymer.json Use bundle: true, in polymer.json instead of an object. 2018-04-25 18:17:52 -07:00
README.md Add the Polymer CLI as devdepency 2018-04-18 19:17:34 +02:00
service-worker.js Address bicknellr comments 2018-04-26 01:16:04 +01:00
sw-precache-config.js Remove last ESLint presence 2018-04-21 13:12:54 +02:00

Polymer App Toolbox - Starter Kit

Build Status

This template is a starting point for building apps using a drawer-based layout. The layout is provided by app-layout elements.

This template, along with the polymer-cli toolchain, also demonstrates use of the "PRPL pattern" This pattern allows fast first delivery and interaction with the content at the initial route requested by the user, along with fast subsequent navigation by pre-caching the remaining components required by the app and progressively loading them on-demand as the user navigates through the app.

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

Migrating from Polymer Starter Kit v1?

Check out our blog post that covers what's changed in PSK2 and how to migrate!

Quickstart

We've recorded a Polycast to get you up and running with PSK2 fast!

Polymer Starter Kit 2 video

Setup

Prerequisites

Install Polymer CLI using npm (we assume you have pre-installed node.js).

npm install -g polymer-cli@next
Initialize project from template
mkdir my-app
cd my-app
polymer init polymer-3-starter-kit

Start the development server

This command serves the app at http://127.0.0.1:8081 and provides basic URL routing for the app:

npm start

Build

The npm run build command builds your Polymer application for production, using build configuration options provided by the command line or in your project's polymer.json file.

You can configure your polymer.json file to create multiple builds. This is necessary if you will be serving different builds optimized for different browsers. You can define your own named builds, or use presets. See the documentation on building your project for production for more information.

The Polymer Starter Kit is configured to create three builds. These builds will be output to a subdirectory under the build/ directory as follows:

build/
  es5-bundled/
  es6-bundled/
  esm-bundled/
  • es5-bundled is a bundled, minified build with a service worker. ES6 code is compiled to ES5 for compatibility with older browsers.
  • es6-bundled is a bundled, minified build with a service worker. ES6 code is served as-is. This build is for browsers that can handle ES6 code - see building your project for production for a list.
  • esm-bundled is a bundled, minified build with a service worker. It uses standard ES module import/export statements for browsers that support them.

Run polymer help build for the full list of available options and optimizations. Also, see the documentation on the polymer.json specification and building your Polymer application for production.

Preview the build

This command serves your app. Replace build-folder-name with the folder name of the build you want to serve.

npm start build/build-folder-name/

Run tests

This command will run Web Component Tester against the browsers currently installed on your machine:

npm test

If running Windows you will need to set the following environment variables:

  • LAUNCHPAD_BROWSERS
  • LAUNCHPAD_CHROME

Read More here daffl/launchpad