Bugfix - Check client function access (_captureRequestSession) #3773
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
dfcook
changed the title
auto-merge was automatically disabled
June 30, 2021 13:33
Head branch was pushed to by a user without write access
kamilogorek
approved these changes
Jul 1, 2021
|
Thanks! |
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.
Our Next.js project is seeing 1000's of errors logged in production:
TypeError GET /^(?!/_next|/static).*$/
client._captureRequestSession is not a function
This is due to the server side code being passed a BrowserClient. This might be due to how we have configured the product, however a simple check on the function being present on the client would resolve.
No tests added as trivial change.
yarn lint) & (yarn test).