Example using unpkg as a immutable web app repository
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
e2e
src
.editorconfig
.gitignore
LICENSE
README.md
angular.json
package-lock.json
package.json
tsconfig.json
tslint.json

README.md

unpkg-immutable-example

Hosting an Immutable Web App with npm, UNPKG, and GitHub Pages

Immutable Web Apps are composed of two concepts:

  • Immutable Assets: Static assets (javascript, CSS, images) that do not contain any environment-specific configuration and are hosted at a permanent, versioned, long-term browser cached location.

  • Deployment Manifest: An index.html that is unique to the environment and not cached by the browser. It contains environment-specific configuration, references to the versioned immutable assets, and meta data.

Using a combination of npm, UNPKG, and Github Pages covers nearly all of these requirements!

  • npm: The software registry stores the the static assets in versioned, immutable packages. Perfect for managing the immutable assets!

  • UNPKG: The CDN makes all assets of the packages on npm addressable over https and globally available. Perfect for delivering the immutable assets!

  • GitHub Pages: This static hosting site supports easy configuration of DNS and HTTPS, has great integration with GitHub (obviously), and has a short TTL for browser caching. Perfect for serving the deployment manifest!

This Immutable Web App is hosted using npm, UNPKG, and GitHub Pages!

Project Structure

The git repository unpkg-immutable-example is split into two critical branches:

  • default is where the Angular project is maintained. It was generated from Angular CLI and is maintained like any other static web application.

  • master is configured to serve the GitHub Pages site. It only contains a single file 404.html. This single file is served for every request made to the GitHub Pages site.

Project Lifecycle

Building

Developing this web application is the same as any other single-page app node project. Features are built and tested locally, commits and pull requests advance the state of the codebase. When a stable version of the app is ready to be deployed, the assets are rendered to the /dist folder using npm run build and new version of the project is published to npm using npm publish. The assets become available on UNPKG.

Deploying

With the new version of the assets available on UNPKG, an atomic deployment can be triggered by switching to the master branch and updating 404.html with the references to the new project assets and any changes to environment variables. Once the commit is is pushed to the GitHub repository, GitHub Pages deployment is triggered and the new version of the web application is available.

Deployments!

With our Immutable Web App hosted by npm/UNPKG and without any environment-specific configuration, deployments are cheap and reliable! Let's deploy index.html to wherever it is easiest to setup DNS and HTTPS!

Deploy to another Github Pages repository

and let's change the version!

Deploy to Netlify

and let's change some environment variables!

  • git clone https://github.com/ImmutableWebApps/unpkg-immutable-deployment
  • cd unpkg-immutable-deployment
  • Create a Netlify account
  • Run npm i -g netlify-cli
  • Run netlify login
  • Run netlify deploy
  • Deployed!

Deploy Locally

and configure it however you want! Try loading up some older versions!

  • git clone https://github.com/ImmutableWebApps/unpkg-immutable-deployment.git
  • cd unpkg-immutable-deployment
  • npm i -g ecstatic
  • ecstatic (ecstatic is a simple static file server)
  • Deployed!