Alex

Also happens on a direct PWA template deployment to Heroku, no `local-npm` installed. I believe it is caused because Heroku runs app as `PRODUCTION` env (and specifically prunes dev modules),...

The reason is `build/build.js` uses chalk. It may be moved into main dependencies, or made optional in `build.js` depending on NODE_ENV (just make sure you do this before forced `process.env.NODE_ENV...

Check the line of error. Most probably your webpack doesn't parse angular-websocket, which utilises require. Upon parse enabling you would face #103

1 year later, still an issue. For me doesn't happen on regular pages, but affects RTL.

Tested, it doesn't make a difference as long as at least a part of an element is caught outside of the footer area. ``` #footer { margin: 0; ... }...

Submitted at https://issues.chromium.org/issues/336164418 My theory is the rendering engine tries to preserve an element in one piece, and pushes it to the "next page" which may work for the regular...