feat(nextjs): Add mechanism to error-logger-caught errors #4061
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
Contributor
size-limit report
|
kamilogorek
suggested changes
Oct 13, 2021
lobsterkatie
force-pushed
the
kmclb-nextjs-add-error-logger-mechanism
branch
2 times, most recently
from
eb5fd80 to
43b839e
Compare
kamilogorek
approved these changes
Oct 20, 2021
lobsterkatie
force-pushed
the
kmclb-nextjs-add-error-logger-mechanism
branch
from
43b839e to
938db78
Compare
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.
Similar to #4046, but this time for errors caught by wrapping the nextjs server's error logger (and this time with data in the correct format*).
Note: This method of capturing errors only works off of vercel.
*That malformed data has been fixed in #4068.