Skip to content

Conversation

ioedeveloper
Copy link
Collaborator

No description provided.

Copy link

netlify bot commented Sep 24, 2025

Deploy Preview for reliable-cocada-166884 ready!

Name Link
🔨 Latest commit 97ec213
🔍 Latest deploy log https://app.netlify.com/projects/reliable-cocada-166884/deploys/68d53f547569870008b86442
😎 Deploy Preview https://deploy-preview-6411--reliable-cocada-166884.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

import { fileSystemUtility, migrationTestData } from '../files/filesystems/fileSystemUtility'
import './styles/preload.css'
import isElectron from 'is-electron'
import { Matomo } from '../plugins/matomo'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wouldn't that slow down the loading? did you notice some latency?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it does not slow it down.

const _paq = (window._paq = window._paq || [])
const matomo = new Matomo(_paq)

window._paq = matomo
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Redefining window._paq here may be tricky, we don't actually know if loader.js has completed its task async loading the tracker code into _paq, and if the window._paq init object has been properly handled by the matomo initializing script. the point of matomo async loading is prevent any delays that would be caused by sync loading the script. so at this point the _paq may just be an array of the init we set in loader, it may not be the tracker at all @yann300 @ioedeveloper

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants