You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add errorFingerprinting config option to disable fingerprinting in browser
Minified browser code produces unstable fingerprints because function
names are mangled, causing the same logical error to generate different
fingerprints across deployments.
- Add errorFingerprinting option to LogfireApiConfigOptions
- Browser SDK defaults to false, Node SDK defaults to true
- Conditionally compute fingerprint in reportError() based on setting
Add `errorFingerprinting` configuration option to control error fingerprint computation
8
+
9
+
Error fingerprinting enables grouping similar errors in the Logfire backend. However, minified browser code produces unstable fingerprints because function names are mangled, causing the same logical error to generate different fingerprints across deployments.
10
+
11
+
- Added `errorFingerprinting` option to `LogfireApiConfigOptions`
12
+
- Browser SDK now defaults to `errorFingerprinting: false`
13
+
- Node SDK keeps the default `errorFingerprinting: true`
14
+
- Users can override the default in either SDK via the `configure()` options
0 commit comments