27 Feb '17, 8am

Turbolinks’ lifecycle explained, or how to marry #ReactJS with #Turbolinks https://t.co/lMJRTrSijD

The whole fun starts, when the user visits a previously cached page. In that case, Turbolinks will emit turbolinks:before-render immediately after caching up the previous page. Then it will replace the body and header tags with the cached version of the page which is being loaded from the server. This operation is concluded with single turbolinks:render event, without firing the load event. When the AJAX call is finished, another turbolinks:before-render event is emmited (for the cached version), and the flow continues as in the uncached version. The load event is called only after rendering the server version of the page.

Full article: http://sevos.io/2017/02/27/turbolinks-lifecycle-explained...