Should the demo site use the production builds?

[jgerigmeyer]

The demo site is currently being bundled and built as a separate build step, which means it isn't actually running the production code. This seems like an easy way to miss production bugs (e.g. #311). I think we should look into having the demo site use the production build of the polyfill.

[jamesnw]

We should consider the e2e tests as well, and make sure in CI the e2e tests are running against a demo site using the built polyfill. Would it be worth setting up an e2e test that would check it works on each flavor of the polyfill? We could either have 4 .html pages or 1 that handles an env flag.

[jgerigmeyer]

We should consider the e2e tests as well, and make sure in CI the e2e tests are running against a demo site using the built polyfill.

Yes, I think that's a good idea. I'd propose that we start by making the demo site use one of the production builds, which in turn will mean the e2e tests (which use the demo site) will also use that build. Then we could add additional HTML files (or an env var) to test the other builds too.