-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Comparing changes
Open a pull request
base repository: getsentry/sentry-javascript
base: 9.37.0
head repository: getsentry/sentry-javascript
compare: 9.38.0
- 15 commits
- 119 files changed
- 9 contributors
Commits on Jul 10, 2025
-
ref(core): Avoid side-effect of & streamline
timestampInSeconds
met……hod (#16890) Related to #16846 This rewrites `timestampInSeconds` to avoid side effects. As a part of this, I also streamlined this a bit to remove special handling for missing `timeOrigin`. If that is missing, we just fall back to using `dateTimestampInSeconds`, instead of doing some custom handling of `timeOrigin` - IMHO that should not be any less accurate, as otherwise we are currently mixing `performance.now` with `Date.now()` which is likely not necessarily accurate either.
Configuration menu - View commit details
-
Copy full SHA for 7be5f79 - Browse repository at this point
Copy the full SHA 7be5f79View commit details -
getsentry-bot committed
Jul 10, 2025 Configuration menu - View commit details
-
Copy full SHA for 8697908 - Browse repository at this point
Copy the full SHA 8697908View commit details -
Merge pull request #16899 from getsentry/master
[Gitflow] Merge master into develop
Configuration menu - View commit details
-
Copy full SHA for 7164cd6 - Browse repository at this point
Copy the full SHA 7164cd6View commit details -
ref(core): Rewrite
logger
to avoid side effects (#16897)Today the logger export from core has a side effect and reads from the global. This PR rewrites this to instead only keep the enabled flag on the carrier. The logger itself is a "normal" method that just looks at the carrier to see if logging is enabled or not.
Configuration menu - View commit details
-
Copy full SHA for fbf7b1c - Browse repository at this point
Copy the full SHA fbf7b1cView commit details -
fix(browser): guard
nextHopProtocol
when adding resource spans (#16900) ref #16804 This was addressed with #16806, but we didn't guard every location that uses `entry.nextHopProtocol`. Will backport to v9 after merge. --------- Co-authored-by: Lukas Stracke <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 6179229 - Browse repository at this point
Copy the full SHA 6179229View commit details -
chore: Add craft entry for @sentry/node-native (#16907)
We need to publish this package!
Configuration menu - View commit details
-
Copy full SHA for 6a245a0 - Browse repository at this point
Copy the full SHA 6a245a0View commit details -
feat(core): Introduce
debug
to replacelogger
(#16906)resolves #16903 ref #16901 This PR introduces a `debug` function that aims to replace `logger`. This gives us a couple of benefits: 1. communicates intent of the export much better 1. avoids collision with `logger` exported from other sdks (which is used for sentry structured logging) 1. we can move structured logging `logger` code into `@sentry/core`, reducing duplication across our sdks We don't deprecate `logger` just yet, we need to convert everything else in the other SDKs first.
Configuration menu - View commit details
-
Copy full SHA for ccbf627 - Browse repository at this point
Copy the full SHA ccbf627View commit details -
Configuration menu - View commit details
-
Copy full SHA for b9db2e6 - Browse repository at this point
Copy the full SHA b9db2e6View commit details
Commits on Jul 11, 2025
-
ref(browser): Unify CLS/LCP recording and add recording event attribu…
…te (#16866) Refactor our CLS and LCP tracking and recording logic. We now have a `listenForWebVitalReportEvents` helper function which listens to page hides and navigation span starts and ensures that the standalone span logic is only called once per web vital. Previously, we had this logic in the CLS and LCP function and it was quite a lot of duplicated and identical code.
Configuration menu - View commit details
-
Copy full SHA for dbdfe48 - Browse repository at this point
Copy the full SHA dbdfe48View commit details -
ref: Avoid
enum
usage (#16922)Apart of directly vendored code, we should avoid `enum`, as it has bundle size impact. Also somehow part of #16846
Configuration menu - View commit details
-
Copy full SHA for 9c7c6bf - Browse repository at this point
Copy the full SHA 9c7c6bfView commit details -
Configuration menu - View commit details
-
Copy full SHA for c7a1e9a - Browse repository at this point
Copy the full SHA c7a1e9aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0dec883 - Browse repository at this point
Copy the full SHA 0dec883View commit details -
Configuration menu - View commit details
-
Copy full SHA for ccf61b2 - Browse repository at this point
Copy the full SHA ccf61b2View commit details -
Merge pull request #16931 from getsentry/prepare-release/9.38.0
meta(changelog): Update changelog for 9.38.0
Configuration menu - View commit details
-
Copy full SHA for 708c73e - Browse repository at this point
Copy the full SHA 708c73eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 64bbf65 - Browse repository at this point
Copy the full SHA 64bbf65View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 9.37.0...9.38.0