There are two ways of adding third party scripts. ‘Embedding’ is ideal for one-off scripts, while ‘global scripts’ loaded on every page.

There are two ways of adding third party scripts. Embedding is ideal for one-off scripts, e.g. widgets.js that is part of embedded tweets (see below). Adding global scripts is for scripts that should be loaded on every page.

Table of Contents

  1. Embedding
  2. Global scripts
  3. async vs. defer vs. loadJSDeferred
    1. Using loadJSDeferred
  4. Registering push state event listeners
  5. Escape hatch


Hydejack supports embedding third party scripts directly inside markdown content. This will work in most cases, except when a script can not be loaded on a page more than once (this will occur when a user navigates to the same page twice).

NOTE: Adding “raw” script tags will make the page slow, unless they have the async or defer attribute set. For more see below.


<script async src="//" charset="utf-8"></script>
<blockquote class="twitter-tweet" data-lang="en">
  <p lang="en" dir="ltr">
    The next version of Hydejack (v6.3.0) will allow embedding 3rd party scripts,
    like the one that comes with this tweet for example.
  &mdash; Florian Klampfer (@qwtel)
  <a href="">June 3, 2017</a>

Global scripts

If you have scripts that should be included on every page you can add them globally by opening (or creating) _includes/my-scripts.html and adding them like you normally would:

<!-- file: _includes/my-scripts.html -->

my-scripts.html will be included at the end of the body tag.

async vs. defer vs. loadJSDeferred

I highly recommended setting the async or defer attribute on your external scripts, otherwise the entire page can’t finish loading until a separate HTTP request is completed, which can take a long time (this applies to the web in general, not just Hydejack).

Specific to Hydejack is the loadJSDeferred function, which is used to load Hydejack’s own scripts. It has various advantages which are detailed in the table below.

Downloadimmediatelyimmediatelyafter document load
Executionasapbefore document loadafter document load
Orderingnonepreserves ordervia callback nesting
SupportIE8+IE9+IE5+ (Hydejack only)

Using loadJSDeferred

Using loadJSDeferred is slightly more work than just adding defer to a script tag.

  loadJSDeferred('<script-src>', function () {
    // <callback code>

If you have scripts that depend on other scripts, you can nest calls, e.g.

  loadJSDeferred('<script-src-1>', function () {
    // <callback script 1>
    loadJSDeferred('<script-src-2>', function () {
      // <callback script 1 + 2>
      loadJSDeferred('<script-src-3>', function () {
        // <callback script 1 + 2 + 3>

Registering push state event listeners

When embedding scripts globally you might want to run some init code after each page load. However, the problem with push state-based page loads is that the load event won’t fire again. Luckily, Hydejack’s push state component exposes an event that you can listen to instead.

<!-- file: _includes/my-scripts.html -->
  document.getElementsByTagName('hy-push-state')[0].addEventListener('hy-push-state-load', function() {
    // <your init code>

Note that the above code must only run once, so include it in your my-scripts.html.

Occurs after clicking a link.
Animation fished and response has been parsed, ready to swap out the content.
The old content has been replaced with the new content.
Special case when animation is finished, but no response from server has arrived yet. This is when the loading spinner will appear.
All embedded script tags have been inserted into the document and have finished loading.

Escape hatch

If you can’t make an external script work with Hydejack’s push state approach to page loading, you can disable push state by adding to your config file:

# file: _config.yml
  no_push_state: true

Continue with Build

© 2017. All rights reserved.

Powered by Hydejack v7.5.0