chore: only load analytics scripts in production or staging environments #7644
Conversation
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
hbuchel
changed the title
katieklein
approved these changes
May 22, 2024
jacoblogan
approved these changes
May 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 of changes:
This PR changes it so our analytics scripts only load in
productionorstagingenvironments. Before, we were loading the testing analytics scripts in all non production environments which caused a very noisy console for local development testing.Testing (hosting)
https://removenonprodscripts.d2bfwhpcsj9awv.amplifyapp.com/
On this test site, my BUILD_ENV variable is set to "staging". So inspecting the DOM, you should see:
Since this preview site's domain doesn't match up there will still be console errors related to those scripts in hosting.
Testing (local)
Currently, when testing locally, the console is very busy with errors related to CSP rules:
After this change the only error left is related to fetchPriority which was introduced in recent version of Next.js vercel/next.js#65161 This is fixed in their canary which currently requires bumping to React 19, so we'll have to wait to address that.
Additionally, there are no shortbread or awshome_s_code related scripts/css loaded.
Related GitHub issue #, if available:
Instructions
If this PR should not be merged upon approval for any reason, please submit as a DRAFT
Which product(s) are affected by this PR (if applicable)?
Which platform(s) are affected by this PR (if applicable)?
Please add the product(s)/platform(s) affected to the PR title
Checks
Does this PR conform to the styleguide?
Does this PR include filetypes other than markdown or images? Please add or update unit tests accordingly.
Are any files being deleted with this PR? If so, have the needed redirects been created?
Are all links in MDX files using the MDX link syntax rather than HTML link syntax?
ref: MDX:
[link](https://docs.amplify.aws/)HTML:
<a href="https://docs.amplify.aws/">link</a>When this PR is ready to merge, please check the box below
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.