documentReady block is triggered before configure has had a chance to run about ahoy.js

[sevab]

Agree with @jsharpe-mr that would be nice to have more granular control over documentReady().

In our case we install & use ahoy via npm/yarn. However, importing the module automatically executes documentReady() and starts it, before we get a chance to set up ahoy with variables necessary for its correct function (e.g. urlPrefix, authentication headers).

At least when building as a node module, would be nice to skip documentReady() to make the library more standalone.

[ankane]

Hey @jsharpe-mr, I think a vast majority of users either don't need to configure Ahoy or are able to configure it before the document is ready, so I don't think it makes sense for all of those users to have to call it manually.

[hwhelchel]

I'm using ahoy.js in webpacker installed via yarn. What is the recommended practice for configuring ahoy.js with this setup?

I think I'm running into the same issue where documentReady runs before I'm able to configure the library.

[zokioki]

I'm also using ahoy.js in a webpacker environment and am facing the same issue. The way I'm handling this is by temporarily assigning the config object to window.ahoy, allowing ahoy to pull that object in on instantiation (see relevant ahoy logic), and resetting window.ahoy to its original value:

initAhoy() {
  // desired configuration
  let ahoyConfig = { cookies: false };

  // back up current window.ahoy value
  let oldAhoy = window.ahoy;

  // assign window.ahoy to the config object, 
  // ahoy.js will use it for configuration once instantiated
  window.ahoy = ahoyConfig;
  this.ahoy = require('ahoy.js').default;

  // restore previous window.ahoy value
  window.ahoy = oldAhoy;
}

I'm not sure if this is the best approach, but it works fairly well for my use case.