|
4 | 4 |
|
5 | 5 | - "You miss 100 percent of the chances you don't take. — Wayne Gretzky" — Michael Scott
|
6 | 6 |
|
| 7 | +## 7.54.0 |
| 8 | + |
| 9 | +### Important Changes |
| 10 | + |
| 11 | +- **feat(core): Add default entries to `ignoreTransactions` for Healthchecks #8191** |
| 12 | + |
| 13 | + All SDKs now filter out health check transactions by default. |
| 14 | + These are transactions where the transaction name matches typical API health check calls, such as `/^.*healthy.*$/` or `/^. *heartbeat.*$/`. Take a look at [this list](https://github.com/getsentry/sentry-javascript/blob/8c6ad156829f7c4eec34e4a67e6dd866ba482d5d/packages/core/src/integrations/inboundfilters.ts#L8C2-L16) to learn which regexes we currently use to match transaction names. |
| 15 | + We believe that these transactions do not provide value in most cases and we want to save you some of your quota by filtering them out by default. |
| 16 | + These filters are implemented as default values for the top level `ignoreTransactions` option. |
| 17 | + |
| 18 | + You can disable this filtering by manually specifiying the `InboundFilters` integration and setting the `disableTransactionDefaults` option: |
| 19 | + ```js |
| 20 | + Sentry.init({ |
| 21 | + //... |
| 22 | + integrations: [new InboundFilters({ disableTransactionDefaults: true })], |
| 23 | + }) |
| 24 | + ``` |
| 25 | + |
| 26 | +- **feat(replay): Add `mutationBreadcrumbLimit` and `mutationLimit` to Replay Options (#8228)** |
| 27 | + |
| 28 | + The previously experimental options `mutationBreadcumbLimit` and `mutationLimit` have been promoted to regular Replay integration options. |
| 29 | + |
| 30 | + A high number of DOM mutations (in a single event loop) can cause performance regressions in end-users' browsers. |
| 31 | + Use `mutationBreadcrumbLimit` to send a breadcrumb along with your recording if the mutation limit was reached. |
| 32 | + Use `mutationLimit` to stop recording if the mutation limit was reached. |
| 33 | + |
| 34 | +- **feat(sveltekit): Add source maps support for Vercel (lambda) (#8256)** |
| 35 | + - feat(sveltekit): Auto-detect SvelteKit adapters (#8193) |
| 36 | + |
| 37 | + The SvelteKit SDK can now be used if you deploy your SvelteKit app to Vercel. |
| 38 | + By default, the SDK's Vite plugin will detect the used adapter and adjust the source map uploading config as necessary. |
| 39 | + If you want to override the default adapter detection, you can specify the `adapter` option in the `sentrySvelteKit` options: |
| 40 | + |
| 41 | + ```js |
| 42 | + // vite.config.js |
| 43 | + export default defineConfig({ |
| 44 | + plugins: [ |
| 45 | + sentrySvelteKit({ |
| 46 | + adapter: 'vercel', |
| 47 | + }), |
| 48 | + sveltekit(), |
| 49 | + ], |
| 50 | + }); |
| 51 | + ``` |
| 52 | + |
| 53 | + Currently, the Vite plugin will configure itself correctly for `@sveltejs/adapter-auto`, `@sveltejs/adapter-vercel` and `@sveltejs/adapter-node`. |
| 54 | + |
| 55 | + **Important:** The SvelteKit SDK is not yet compatible with Vercel's edge runtime. |
| 56 | + It will only work for lambda functions. |
| 57 | + |
| 58 | +### Other Changes |
| 59 | + |
| 60 | +- feat(replay): Throttle breadcrumbs to max 300/5s (#8086) |
| 61 | +- feat(sveltekit): Add option to control handling of unknown server routes (#8201) |
| 62 | +- fix(node): Strip query and fragment from request URLs without route parameters (#8213) |
| 63 | +- fix(remix): Don't log missing parameters warning on server-side. (#8269) |
| 64 | +- fix(remix): Pass `loadContext` through wrapped document request function (#8268) |
| 65 | +- fix(replay): Guard against missing key (#8246) |
| 66 | +- fix(sveltekit): Avoid capturing redirects and 4xx Http errors in request Handlers (#8215) |
| 67 | +- fix(sveltekit): Bump `magicast` to support `satisfied` keyword (#8254) |
| 68 | +- fix(wasm): Avoid throwing an error when WASM modules are loaded from blobs (#8263) |
| 69 | + |
7 | 70 | ## 7.53.1
|
8 | 71 |
|
9 | 72 | - chore(deps): bump socket.io-parser from 4.2.1 to 4.2.3 (#8196)
|
|
0 commit comments