I am not familiar with Turbolinks, but in general based on their GitHub readme that states that "you can't rely on DOMContentLoaded or jQuery.ready() to trigger your code", I would think that it severely impedes extensions that rely on these events as they run when the page loads.
Specifically in this instance, since Turbolinks replaces the body content, it disrupts the CrossriderAPI library that utilizes the DOM content for its operation. Hence, without considerable reworking of the code, I don't think that Turbolinks can co-exist with the CrossriderAPI and can disrupt with extension functionality.