🛠 Status: Experimental

pwa-lit-template is currently in development.

This project helps you to build Progressive Web Applications following the modern web standards, best practices and providing you with tools for that purpose. Out of the box, provides you with the following features:

• Simple way to create Web Components with LitElement.
• Small and powerful client-side router for Web Components with Vaadin Router.
• All the benefits from a PWA (manifest, service worker, offline UI) thanks to Workbox and pwa-helpers.
• SEO friendly thanks to the PageElement custom element and the html-meta-manager.
• A development server with auto-reload to serve the application without bundling the code with es-dev-server.
• Simple build flow thanks to Rollup and @open-wc/building-rollup initial configuration.
• Easy deployment over to prpl-server or any static hosting.

• node.js

Furthermore, this project is built on TypeScript with the intention of improving the developer experience.

npm install

This command serves the app at http://localhost:8000:

npm start

The folder that es-dev-server will serve running this command will be src-js/, a compiled version from TypeScript that will output plain JavaScript, without any transformation from the build process.

├─ images/
├─ patches/
├─ server/
├─ src/
│  ├─ components/
│  │  ├─ app-index.ts
│  │  └─ ···
│  ├─ config/
│  ├─ helpers/
│  │  ├─ page-element.ts
│  │  └─ ···
│  ├─ pages/
│  │  ├─ page-home.ts
│  │  └─ ···
│  └─ router/
│     └─ routes.ts
├─ index.html
├─ manifest.webmanifest
├─ package.json
├─ robots.txt
├─ rollup.config.js
└─ tsconfig.json

• images: is use to store the static resourced used by your application.
• patches: contains the patches to apply in the different packages mentioned here. It will be removed at some point.
• server: contains the logic to serve the application. And is where you are going to create your dist/ folder containing the bundle of your application.
• src
  • components: contains your custom Web Components. Inside this folder you will find the app-index.ts file, main root of your application following the PRPL patern.
  • config: stores the configuration (handles the environment at the build time).
  • helpers: contains two interesting features: PageElement and html-meta-manager. Go more in-depth with them here.
  • pages: where you create the pages for your application.
  • router: where you create the routes for your application.
• index.html: the application entry point.

This command use Rollup to build an optimized version of the application for production:

npm run build

It has two outputs: in addition to outputting a regular build, it outputs a legacy build which is compatible with older browsers down to IE11.

At runtime it is determined which version should be loaded, so that legacy browsers don't force to ship more and slower code to most users on modern browsers.

Note: If you need to add static files to the build, like the images folder or the manifest.webmanifest, you should register them in the copy() plugin of the rollup.config.js.

1. Create the new page component (extending from PageElement helper) in the pages folder. For example a page-explore.ts.

   import { html, customElement } from 'lit-element';
   
   import { PageElement } from '../helpers/page-element';
   
   @customElement('page-explore')
   export class PageExplore extends PageElement {
     render() {
       return html`
         <h1>Explore</h1>
         <p>My new explore page!</p>
       `;
     }
   }

2. Register the new route in the routes.ts:

   {
     path: '/explore',
     name: 'explore',
     component: 'page-explore',
     metadata: {
       title: 'Explore',
       description: 'Explore page description'
     },
     action: async () => {
       await import('../pages/page-explore');
     }
   },

With SEO in mind, this project offers you the PageElement base class to help you to deal with it; it has a metadata() method that edits the HTML meta tags of the specific page with the metadata property defined in the route. And if you need dynamic information, you also can override the metadata() method.

• Chrome
• Edge
• Firefox
• Safari

To run on other browsers, you need to use a combination of polyfills and transpilation. This step is automated by the build for production command.

• There is a patch that modifies the @vaadin/router's scroll standard behavior to have a more consistent scroll; now when you perform a click event, the scroll will be reset to the top position.

  Related issue: #1: Remove the Vaadin Router patch