Gracefully handle telemetry not being available #44986
Merged
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
1 task
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.
It seems there is an issue with yarn v3 where the exports for our
traceGlobalsmay not be set as we expect causing calls totelemetry.record()to hang the build process since webpack stalls when an uncaught exception is thrown in a plugin.Verified on the reproduction repo manually as well via
yarn add next@https://files-620kx9vw0-vtest314-ijjk-testing.vercel.app/next-v13.1.3-canary.3.tgzBug
fixes #numbercontributing.mdFixes: #44976