- Publishing (actually packing) will now generate the typings and fail
if they don't compile.
- Travis will now generate the typings and fail if they don't compile.
- Some minor tweaks to get typings compiling.
* Use containers for testing again
Disable chrome security sandbox due to travis-ci/travis-ci#8836
Remove node module caching with the removal of package lock
* flag is "no-sandbox"
* Add back npm cache
* Use sudo to fix chrome testing
There is a bug with the chrome sandbox in the Travis CI container
system, which is fixed by using `sudo: required`.
Related to travis-ci/travis-ci#8836
* reduce cognitive overhead of the test runner
* remove testing polyfilled Custom Elements with native ShadowDOM
* Use headless chrome and firefox
Use MacOS 10.13 for Safari 11
* disable testing CSS Custom Property Shim
* move sauce tests into script for travis_wait compat
* [ProperitesChanged] Fix deserialization
A change merged with the `basic-element` caused the `type` argument to `_deserializeValue` to be called as a function to determine the deserialized output. This was an unintended breaking change from master and is reverted here. For example, the `basic-element` change regressed using a class constructor as a property type.
* Remove cruft
* Update docs
* Test verbose wct output on firefox
* Avoid Chrome and FF running in parallel on Travis to avoid timeouts.
