-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Remove unsupported ga-lite and update existing calls to GA4 #6366
Conversation
Size changes📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 🎉 Global Bundle Size Decreased
DetailsThe 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 If you want further insight into what is behind the changes, give @next/bundle-analyzer a try! Three Pages Changed SizeThe following pages changed size from the code in this PR compared to its base branch:
DetailsOnly 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 Any third party scripts you have added directly to your app using the Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 10% or more, there will be a red status indicator applied, indicating that special attention should be given to this. |
const terminationEvent = 'onpagehide' in window ? 'pagehide' : 'unload'; | ||
window.addEventListener(terminationEvent, function () { | ||
ga('send', 'timing', 'JS Dependencies', 'unload'); | ||
// @ts-ignore |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you install the gtag typescript typtes instead of a ts-ignore
here? I think yarn add @types/gtag.js --dev
should do the trick.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh nice! I can follow up and add this in a separate PR
|
||
import '@docsearch/css'; | ||
import '../styles/algolia.css'; | ||
import '../styles/index.css'; | ||
import '../styles/sandpack.css'; | ||
|
||
if (typeof window !== 'undefined') { | ||
if (process.env.NODE_ENV === 'production') { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was this check removed? Does this mean that PR preview deploys and locally hosted environments will now send GA4 events?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This check was for the two deprecated ga calls that were also removed so it's no longer needed
We recently updated our GA tag to include GA4 in this PR
These changes removes the no longer used
ga-lite
, and updates it to usegtag
instead sincega-lite
is no longer supported.I've also updated
NEXT_PUBLIC_GA_TRACKING_ID
to the new ID, and removed it fromsrc/siteConfig.js
Test plan