fix(insights): am1 customers should not see laravel and nextjs pages #101438
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
github-actions
bot
added
the
Scope: Frontend
DominikB2014
deleted the
dominikbuszowiecki/browse-72-javascript-user-feedback-web-vitals-and-pageloads-not
branch
chromy
pushed a commit
that referenced
this pull request
Oct 17, 2025
…101438) Am1 customers should not see laravel/nextjs pages, I believe any customers that doesn't have eap (which is only am1), should not see laravel/nextjs.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Am1 customers should not see laravel/nextjs pages, I believe any customers that doesn't have eap (which is only am1), should not see laravel/nextjs.