chore: delete Sentry #292
Merged
chore: delete Sentry #292
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Merged
steveluscher
added a commit
that referenced
this pull request
Sep 15, 2023
chore: format code --- Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/solana-labs/explorer/pull/291). * #292 * __->__ #291
# Summary One of the central tenets of measurement is this question: are you prepared to change what you work on based on the outcome of the data. Explorer is not under the kind of active development that requires deep insights into runtime data at this time. Put another way, I personally have never performed work on the Explorer based on a result that I observed in Sentry. Until this changes, let's get rid of it.
|
This seems to have taken first-load JS on the homepage from 217 kB to 171kB. Lighthouse score is approaching 90%. |
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.
chore: delete Sentry
Summary
One of the central tenets of measurement is this question: are you prepared to change what you work on based on the outcome of the data.
Explorer is not under the kind of active development that requires deep insights into runtime data at this time. Put another way, I personally have never performed work on the Explorer based on a result that I observed in Sentry.
Until this changes, let's get rid of it.