On initial page load run init before turbo:load has been fired

[indykoning]

This will make Rapidez initialize before marketing scripts, browser extensions and other scripts run.
Improving startup times of Rapidez.

Before:

After:

Currently as draft as we should figure out the best method/event to run this on in order not to impact LCP

[indykoning]

After the last commit the LCP is no longer impacted.
We no longer fire before ALL browser extensions, but we do fire earlier.
After:

Also i've placed more in timeouts and animation frames, so they schedule their own tasks instead of putting it all on a task that's already taking too long

This is what it looks like without browser extensions now:

As you can see Vue bootup is even decoupled from the onload event. onload can be fired before or after vue has booted depending on external factors

[indykoning]

This specific order of setTimeout and requestAnimationFrame ensures LCP is not impacted.
And ensures small task time for the turbo:load/evaluate script, and vue:loaded events by scheduling them all in their own task.

Using a setTimeout for both, a requestAnimationFrame for both, or executing this immediately and booting Vue in a requestAnimationFrame all has impact on the LCP

[royduin]

So this is still work in progress? Is it tested within a real project?

[indykoning]

Yes it has been tested (though locally) with both a clean Rapidez installation, and a couple of real projects without issue.
Though i'm struggling with the tests

[royduin]

I'll change it to a draft, please mark it when it's ready to merge

[indykoning]

It seems the tests were caused by the order that event listeners were being applied in.
Vue could not prevent the event listener for turbolinks causing a navigation before the vue events were fired.

Loading turbo lazily fixes this issue.