Update feat/next-js branch #3366
Merged
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
Clarified how the browser SDK is integrated with the other SDKs
…in (#3320) Bumps [elliptic](https://github.com/indutny/elliptic) from 6.5.3 to 6.5.4. - [Release notes](https://github.com/indutny/elliptic/releases) - [Commits](indutny/elliptic@v6.5.3...v6.5.4) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [elliptic](https://github.com/indutny/elliptic) from 6.5.3 to 6.5.4. - [Release notes](https://github.com/indutny/elliptic/releases) - [Commits](indutny/elliptic@v6.5.3...v6.5.4) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Update gatsby-node.js * remove additional vercel fallbacks
* misc: 6.2.3 changelog * add whitespace I'm embarrassing myself
* ref: Add fast-path to fetchImpl * fix: Cleanup after fetch impl detection
* fix: Add SentryRequestType to RateLimitingCategory mapping * Update remaining tests
…#3347) * ref(ember): Fix tests to be forward compatible with component changes One of the frameworks provided components, link-to, had a change to it's internal name. It's not really relevant to the test, so normalizing the description should work across the version changes.
* ref(ember): Silence deprecation warnings in beta We can deal with deprecations once they hit mainline, this should hopefully silence deprecations in the scenarios so we can see failures more easily and not spit out too many logs
…tion.prototype.query (#3353)
Try to use the best of performance.timeOrigin or performance.timing.navigationStart as long as they are near the current time reported by Date.now. The intention is to mitigate transactions that are reported with a huge time skew, particularly from Firefox. This is trying to address the inconsistencies between browsers by always trying to use timeOrigin first, as long as its consistent with the current time, otherwise, use the navigationStart if its consistent with the current time, eventually fallback to date if all else fails. We also remember what source is used for the time origin, so we can tag events and analyze later. Co-authored-by: Rodolfo Carvalho <[email protected]> Co-authored-by: Alberto Leal <[email protected]>
size-limit report
|
iker-barriocanal
approved these changes
Apr 2, 2021
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.
This aims to keep the branch up-to-date by merging master onto it.
There was a merge conflict in
yarn.lock, I am not sure I resolved it in the best way (I runyarnto re-generate the lock file). Still, there are just so many changes that I don't know are really required for the@sentry/nextjsSDK.After merging master in, I noticed there are still several places to clean up before we can merge
feat/next-jsintomaster.And there are a few small changes that we could merge into master without waiting for the
@sentry/nextjsSDK to land, thus reducing the patch for adding the new SDK to a minimum.