meteor3: raven -> @sentry/node + @sentry/browser
flowkey:raven (Sentry legacy SDK) is dead on Meteor 3 and, with the old sentry.comunes.org DSN unreachable, spammed the boot log with 502s on every exception. Replaced by the modern SDKs (8.x) behind the same ravenLogger.log() facade so the 6 call sites are unchanged. Empty DSN -> plain console logger (same behavior as before). End-to-end verified against a real backend: GlitchTip deployed on aaron (Sentry-compatible, fits in ~1.5GB vs Sentry's 16GB), fronted at sentry.comunes.org. A test exception sent from the dev server appeared in GlitchTip within seconds. REST smoke byte-identical (12/12).
This commit is contained in:
parent
197a59f641
commit
4ca7e198d3
7 changed files with 1184 additions and 96 deletions
|
|
@ -8,6 +8,8 @@
|
|||
"dependencies": {
|
||||
"@babel/runtime": "^7.29.7",
|
||||
"@cleverbeagle/dates": "^0.5.1",
|
||||
"@sentry/browser": "^8.55.2",
|
||||
"@sentry/node": "^8.55.2",
|
||||
"@turf/buffer": "^5.1.5",
|
||||
"babel-runtime": "^6.26.0",
|
||||
"bcrypt": "^5.1.1",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue