Fix PostHog.register TypeError by ensuring execution after window load#3234
Merged
Conversation
joepavitt
approved these changes
May 9, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes an issue where
posthog.registerwas not recognized as a function. The solution ensures that the code runs only after the window load event, guaranteeing that all resources, including the PostHog library, are fully initialized.This also updates the PostHog snippet to its most recent version.
This solution can only be tested locally, you need to remove the
{%- if not DEV_MODE -%}condition that wraps the last block in the filebase.njkRelated Issue(s)
Checklist