Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix PostHog frontend distinctId error #609

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

luis-herasme
Copy link
Member

@luis-herasme luis-herasme commented Oct 29, 2024

Checklist

  • My change requires a documentation update, and I have done it.
  • I have added tests to cover my changes.
  • I have filled out the description and linked the related issues.

Description

This PR fixes an issue where PostHog wasn’t working on the frontend because distinctId was missing. The distinctId is set on the backend with a cookie, but that cookie wasn’t accessible on the frontend, which led to tracking issues. This update makes sure the frontend can access the distinctId.

Copy link

changeset-bot bot commented Oct 29, 2024

⚠️ No Changeset found

Latest commit: cdde604

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Oct 29, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
blobscan-staging ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 31, 2024 9:15pm
5 Skipped Deployments
Name Status Preview Comments Updated (UTC)
blobscan-docs ⬜️ Ignored (Inspect) Visit Preview Oct 31, 2024 9:15pm
blobscan-gnosis ⬜️ Ignored (Inspect) Visit Preview Oct 31, 2024 9:15pm
blobscan-holesky ⬜️ Ignored (Inspect) Visit Preview Oct 31, 2024 9:15pm
blobscan-mainnet ⬜️ Ignored (Inspect) Visit Preview Oct 31, 2024 9:15pm
blobscan-sepolia ⬜️ Ignored (Inspect) Visit Preview Oct 31, 2024 9:15pm

Copy link

codecov bot commented Oct 29, 2024

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 89.07%. Comparing base (37c311c) to head (cdde604).
Report is 10 commits behind head on main.

Files with missing lines Patch % Lines
packages/api/src/context.ts 0.00% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #609      +/-   ##
==========================================
+ Coverage   88.93%   89.07%   +0.14%     
==========================================
  Files         154      155       +1     
  Lines       10283    10425     +142     
  Branches     1142     1170      +28     
==========================================
+ Hits         9145     9286     +141     
- Misses       1138     1139       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

Choose a reason for hiding this comment

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

This integration is designed for Nextjs apps that use an app router not a pages one. We should be doing something similar to this.

Also, can we implement the integration in TS?

@luis-herasme luis-herasme changed the title Refactor posthog and fix distinctId Fix PostHog frontend distinctId error Oct 31, 2024
Copy link
Contributor

📦 Next.js Bundle Analysis for @blobscan/web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page Size (compressed)
global 334.17 KB (🔴 +88.55 KB)
Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

New Pages Added

The following pages were added to the bundle from the code in this PR:

Page Size (compressed) First Load % of Budget (350 KB)
/block_neighbor 251 B 334.41 KB 95.55%
/stats 347.54 KB 681.71 KB 194.77%

Eight Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load % of Budget (350 KB)
/ 351.65 KB 685.82 KB 195.95% (🟢 -5.06%)
/address/[address] 26.8 KB 360.97 KB 103.13% (🟢 -4.83%)
/blob/[hash] 27.5 KB 361.67 KB 103.33% (🟢 -4.26%)
/blobs 76.74 KB 410.91 KB 117.40% (🟡 +12.55%)
/block/[id] 14.17 KB 348.34 KB 99.53% (🟢 -4.20%)
/blocks 74.44 KB 408.61 KB 116.75% (🟡 +12.53%)
/tx/[hash] 16.61 KB 350.78 KB 100.22% (🟡 +0.96%)
/txs 73.94 KB 408.11 KB 116.60% (🟡 +10.53%)
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

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.

2 participants