Turbo Router

Turbo Router

Learn how links are routed using the AJAX framework.

A feature included with the AJAX framework extra features is an implementation of PJAX (push state and AJAX) called the turbo router. It gives the performance benefits of a single page application without the added complexity of a client-side framework. When you click a link, the page is automatically swapped client-side without the cost of a full page load. You may programmatically visit a link with the following.


To replace the current URL without adding it to the navigation history, similar to window.history.replaceState, set the action option to replace.

oc.visit(location, { action: 'replace' });

To check if the turbo router is enabled and should be used.

if (oc.useTurbo && oc.useTurbo()) {
    // Use PJAX

# Disable Routing

To disable PJAX routing on a specific page, you may trigger a full reload by including the turbo-visit-control meta tag in the head section of the page with the reload value. This will disable the feature for incoming requests only.

    <meta name="turbo-visit-control" content="reload" />

To completely disable PJAX in your website, set the value to disable. This will disable the feature for all incoming and outgoing requests.

<meta name="turbo-visit-control" content="disable" />

By default, all internal HTML links will be routed using PJAX, but you can disable this by marking links or their parent container with data-turbo="false". Links that are disabled are handled normally by the browser.

<a href="/" data-turbo="false">Disabled</a>

You may re-enable when an ancestor has disabled:

<div data-turbo="false">
    <a href="/" data-turbo="true">Enabled</a>

# Persisting Page Elements

In some cases you may want to include static elements on the page, these are elements that should not be refreshed when the page updates. Use the data-turbo-permanent attribute on the parent element. The element must also supply and id attribute so the original page can be matched with the new page, including event listeners.

<div id="main-navigation" data-turbo-permanent>...</div>

# Detecting a Cached Page Load

You can detect when the page contents are sourced from the cache with the data-turbo-preview attribute on the HTML element. Expressed in JavaScript as:

if (document.documentElement.hasAttribute('data-turbo-preview')) {
    // Page shown is loaded from cache

Or using a StyleSheet:

html[data-turbo-preview] {
    /* Hide overlays from previous view */

# Setting a Root Path

By default, PJAX is used for all links within the same domain name and a visit to any other URL will fallback to a full page load. In some cases, your application may live in a subdirectory and the links should only apply to the root path.

For example, if you website lives in /app and you don't want the links to apply to a different site in /docs then you may restrict the links to a root path. You may set the root path by including the turbo-root meta tag in the page's head section.

    <meta name="turbo-root" content="/app">

# Working with JavaScript

When working with PJAX, the page contents may load dynamically, which differs from the usual browser behavior. To overcome this, use the page:loaded event handler is called every time the page loads.

addEventListener('page:loaded', function() {
    // Page has rendered something new

# Making Controls Idempotent

When a page visit occurs and JavaScript components are initialized, it is important that these function are idempotent. In simple terms, an idempotent function is safe to apply multiple times without changing the result beyond its initial application.

One technique for making a function idempotent is to keep track of whether you've already performed it by adding a value to the dataset property on each processed element.

addEventListener('page:loaded', function() {
    // Find my control
    var myControl = document.querySelector('.my-control');

    // Halt because it has already been initialized
    if (myControl.dataset.hasMyControl) {

    // Initialize since this is the first time
    myControl.dataset.hasMyControl = true;

Another simpler approach is to allow the function to run multiple times and apply idempotence techniques internally. For example, check to see if a menu divider already exists first before creating a new one.

# Disposing Controls

In some cases you may bind global events for a specific page only, for example, binding a hot key to a certain action.

addEventListener('keydown', myKeyDownFunction);

To prevent this event from leaking to other pages, you should remove the event using the page:unload method, which will destroy any events and controls. The event can be used once to dispose of controls and events safely.

addEventListener('page:unload', function() {
    removeEventListener('keydown', myKeyDownFunction);
}, { once: true });

# Global Events

The AJAX framework triggers several events during the navigation lifecycle and page responses. The events are usually triggered on the document object with details available on the event.detail property.

Event Description
page:click triggered when a turbo-routed link is clicked.
page:before-visit triggered before visiting a location, except when navigating using browser history.
page:visit triggered after a clicked visit starts.
page:request-start triggered before the request for a page.
page:request-end triggered after the page request ends.
page:before-cache triggered before a page is cached.
page:before-render triggered before the page content is rendered.
page:render triggered after the page is rendered. This is fired twice, once from cache and once again after requesting the new page content.
page:load triggered once after the initial page load and again every time a page is visited.
page:loaded identical to page:load except will wait for all newly added scripts to load.
page:unload called when a previously loaded page should be disposed.

# Usage Examples

The following JavaScript will run every time a page loads.

addEventListener('page:load', function() {
    // ...

# Working with Hot Reloading

In some cases, the turbo router may interfere when you are developing your website with hot reloading or browser sync technology, such as with Laravel Mix (opens new window) in development mode using laravel-mix & browsersync. To overcome this add the following code to your webpack browserSync configuration.

snippetOptions: {
    rule: {
        match: /<\/head>/i,
        fn: function (snippet, match) {
            return '<meta name="turbo-visit-control" content="disable" />';