Improve handling around performance navigation entry #74
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.
Older browsers do not have support for PerformanceNavigationTiming. This changes adds fallback for getting navigation type from the deprecated
window.performance.navigation.type
when PerformanceNavigationTiming is not available.Since
activationStart
is also on PerformanceNavigationTiming, we move this into a helper in the same file as well.Finally, we can override the built-in browser declarations to get better typing for
getEntriesByType
,activationStart
, anddocument.prerendering
. This allows us to remove the override for@typescript-eslint/ban-ts-comment
eslint rule since the default is pretty reasonable (ts-expect-error
is allowed with description) https://typescript-eslint.io/rules/ban-ts-comment/