Bump the development-dependencies group across 1 directory with 2 updates

[dependabot]

Bumps the development-dependencies group with 2 updates in the / directory: vitest and @sentry/bundler-plugins.

Updates vitest from 5.0.3 to 5.0.4

Release notes

Sourced from vitest's releases.

v5.0.4

   🚀 Features

• experimental:
  • Tag cache directories with CACHEDIR.TAG  -  by @​lifeiscontent in vitest-dev/vitest#11461 (a8ea3)
  • Support test.ui.theme option  -  by @​sheremet-va in vitest-dev/vitest#11499 (1da66)
  • Highlight selector multiple matches in trace view  -  by @​hi-ogawa, Hiroshi Ogawa and Claude Opus 5.5 in vitest-dev/vitest#11489 (5abba)
  • Print how many tests were affected and a total when running --changed  -  by @​sheremet-va in vitest-dev/vitest#11424 (a2336)
  • Add an option to cache dependencies instead of statically parsing them  -  by @​sheremet-va in vitest-dev/vitest#11515 (c0601)
  • Add fit and zoom controls to trace viewer  -  by @​hi-ogawa, Hiroshi Ogawa and Claude Opus 5.5 in vitest-dev/vitest#11490 (f5dd9)

   🐞 Bug Fixes

• Fail the run on git and location filter errors  -  by @​sheremet-va in vitest-dev/vitest#11430 (30d03)
• Enable fsModuleCache by default  -  by @​sheremet-va in vitest-dev/vitest#11435 (ad208)
• Track project files and mocks with --changed  -  by @​sheremet-va in vitest-dev/vitest#11432 (b0f2b)
• Refactor caching, fix : in project and change the shape of results cache  -  by @​sheremet-va in vitest-dev/vitest#11453 (9673c)
• Keep full $ string values when taskTitleValueFormatTruncate is 0  -  by @​hi-ogawa, Hiroshi Ogawa and Claude Opus 5.5 in vitest-dev/vitest#11485 (4f7e1)
• Resolve node builtins in client environments  -  by @​sheremet-va in vitest-dev/vitest#11417 (56b31)
• Fix module graph builtin externals after #11421  -  by @​hi-ogawa, Hiroshi Ogawa and Claude Opus 5.5 in vitest-dev/vitest#11491 and vitest-dev/vitest#11421 (008e1)
• Wrap module mocks during in-source testing  -  by @​sheremet-va in vitest-dev/vitest#11505 (36d19)
• Handle line endings in snapshot  -  by @​sheremet-va in vitest-dev/vitest#11522 (4c468)
• Respect root in projects  -  by @​sheremet-va in vitest-dev/vitest#11521 (26642)
• Resolve mocks in directories with spaces  -  by @​sheremet-va in vitest-dev/vitest#11539 (caaef)
• api:
  • Publish the api token atomically  -  by @​umairnawaz333 in vitest-dev/vitest#11323 (6f990)
• browser:
  • Close the mock route interception race  -  by @​cplieger and @​sheremet-va in vitest-dev/vitest#8339 and vitest-dev/vitest#11083 (d6620)
  • Allow toHaveTextContent without arguments  -  by @​nomadical in vitest-dev/vitest#11425 (8ebcf)
  • Apply API options without browser config  -  by @​sheremet-va in vitest-dev/vitest#10852 (ad055)
  • Preserve undefined command arguments  -  by @​sheremet-va and @​AriPerkkio in vitest-dev/vitest#11497 (1576d)
  • Wait for setup mocks before importing a test file  -  by @​kasperpeulen in vitest-dev/vitest#11520 (b61d1)
  • Avoid extra scroll outside the iframe  -  by @​sheremet-va in vitest-dev/vitest#11523 (662e8)
  • Run browser instances as workers  -  by @​sheremet-va in vitest-dev/vitest#11525 (bf04b)
    • ⚠️ This can degrade performance if you have a custom maxWorkers setting. Previously, it was applied incorrectly and could lead to Vitest using too many resources. For example, a lower number would still open too many browsers. Fixing it means Vitest opens less instances by default now.
  • Open one cdp session per tester  -  by @​sheremet-va in vitest-dev/vitest#11542 (69e63)
  • Clean up unmocked and pending mocks  -  by @​sheremet-va in vitest-dev/vitest#11537 (5c955)
• coverage:
  • V8 browser memory leak between test files  -  by @​AriPerkkio in vitest-dev/vitest#11466 (2297d)
  • allowExternal fails to include uncovered files  -  by @​AriPerkkio in vitest-dev/vitest#11513 (4ef00)
  • Filenames containing brackets incorrectly showing as uncovered  -  by @​AriPerkkio in vitest-dev/vitest#11531 (0fa80)
  • Istanbul coverage wrong when module transform warmups  -  by @​AriPerkkio in vitest-dev/vitest#11529 (9f61d)
• deps:
  • Update all non-major dependencies  -  by @​sheremet-va in vitest-dev/vitest#11167 (c74e0)
• expect:
  • Fix Map and Set deep equality in some assertions  -  by @​hi-ogawa, Hiroshi Ogawa and Claude Opus 5.5 in vitest-dev/vitest#11402 (b4e79)
  • Check value in chai-style returned  -  by @​sheremet-va in vitest-dev/vitest#11500 (1aca0)
• mocker:
  • Fix native loader mocking edge cases  -  by @​sheremet-va in vitest-dev/vitest#11540 (cd423)
• pretty-format:

... (truncated)

Commits

• 6a11cf6 chore: release v5.0.4 (#11554)
• 58c86ed chore(deps): update all non-major dependencies (#11550)
• 0fa80f5 fix(coverage): filenames containing brackets incorrectly showing as uncovered...
• bf04b9c fix(browser): run browser instances as workers (#11525)
• 3e3624c refactor: resolve maxWorkers once in config (#11524)
• 26642f7 fix: respect root in projects (#11521)
• c06012a feat(experimental): add an option to cache dependencies instead of statically...
• 4ef000a fix(coverage): allowExternal fails to include uncovered files (#11513)
• 1da6640 feat: support test.ui.theme option (#11499)
• b618afd fix(vm): bind this to module.exports (#11504)
• Additional commits viewable in compare view

Updates @sentry/bundler-plugins from 11.4.0 to 11.7.0

Release notes

Sourced from @​sentry/bundler-plugins's releases.

11.7.0

Important Changes

• feat(cloudflare): Add opt-in cron monitoring for Cron Triggers (#25014)

  The new cronTriggersIntegration sends check-ins for Cron Triggers. Each check-in includes the schedule from controller.cron, so Sentry creates the monitor on the first run. The integration is opt-in, because monitors are billed.

  Cron Triggers have no names, so map each cron expression of your wrangler config to a monitor slug. With the Sentry Cloudflare Vite plugin, add the integration to src/instrument.server.ts:

  // src/monitorSlugs.ts
  export const monitorSlugs: Record<string, string> = {
    '30 9 * * MON-FRI': 'daily-report',
  };
  // src/instrument.server.ts
  import * as Sentry from '@​sentry/cloudflare';
  import { monitorSlugs } from './monitorSlugs';
  export default Sentry.defineCloudflareOptions(env => ({
  dsn: env.SENTRY_DSN,
  integrations: [Sentry.cronTriggersIntegration({ monitorSlug: cron => monitorSlugs[cron] })],
  }));
  // src/index.ts
  import { monitorSlugs } from './monitorSlugs';
  export default {
  async scheduled(controller, env) {
  switch (monitorSlugs[controller.cron]) {
  case 'daily-report':
  // Your daily report job
  break;
  }
  },
  };

  The monitorSlug function can also return monitor settings, for example { monitorSlug: 'daily-report', maxRuntime: 30 }, or undefined to send no check-ins for a trigger. Without monitorSlug, the SDK derives the slug from the cron expression. If you deploy with wrangler directly, pass the same integration to Sentry.withSentry.

• feat(node): Add neonIntegration for @​neondatabase/serverless (#25164, #25176)

  The new neonIntegration creates db spans for queries of the @neondatabase/serverless driver: for the WebSocket Client and Pool, and for the HTTP neon() function. This includes the neon-http and neon-serverless adapters of Drizzle. The integration is on by default when tracing is enabled.

• feat(node): Stop sending the process session once request sessions are tracked (#24915)

  Node servers sent release health data two times: as request session aggregates, and as the process session of processSessionIntegration. An error in a request also marked the process session as errored, so the SDK counted the error two times. Now the SDK drops the process session when it tracks the first request session. Scripts, CLIs and workers that do not serve requests keep the process session, and so do servers with httpServerIntegration({ sessions: false }). This changes the release health numbers of Node servers, because they no longer send the errored or crashed update of the process session.

• feat(server-utils): Record decide calls as gen_ai.decide spans (#25270, #25272, #25274, #25281)

... (truncated)

Changelog

Sourced from @​sentry/bundler-plugins's changelog.

11.7.0

Important Changes

• feat(cloudflare): Add opt-in cron monitoring for Cron Triggers (#25014)

  The new cronTriggersIntegration sends check-ins for Cron Triggers. Each check-in includes the schedule from controller.cron, so Sentry creates the monitor on the first run. The integration is opt-in, because monitors are billed.

  Cron Triggers have no names, so map each cron expression of your wrangler config to a monitor slug. With the Sentry Cloudflare Vite plugin, add the integration to src/instrument.server.ts:

  // src/monitorSlugs.ts
  export const monitorSlugs: Record<string, string> = {
    '30 9 * * MON-FRI': 'daily-report',
  };
  // src/instrument.server.ts
  import * as Sentry from '@​sentry/cloudflare';
  import { monitorSlugs } from './monitorSlugs';
  export default Sentry.defineCloudflareOptions(env => ({
  dsn: env.SENTRY_DSN,
  integrations: [Sentry.cronTriggersIntegration({ monitorSlug: cron => monitorSlugs[cron] })],
  }));
  // src/index.ts
  import { monitorSlugs } from './monitorSlugs';
  export default {
  async scheduled(controller, env) {
  switch (monitorSlugs[controller.cron]) {
  case 'daily-report':
  // Your daily report job
  break;
  }
  },
  };

  The monitorSlug function can also return monitor settings, for example { monitorSlug: 'daily-report', maxRuntime: 30 }, or undefined to send no check-ins for a trigger. Without monitorSlug, the SDK derives the slug from the cron expression. If you deploy with wrangler directly, pass the same integration to Sentry.withSentry.

• feat(node): Add neonIntegration for @​neondatabase/serverless (#25164, #25176)

  The new neonIntegration creates db spans for queries of the @neondatabase/serverless driver: for the WebSocket Client and Pool, and for the HTTP neon() function. This includes the neon-http and neon-serverless adapters of Drizzle. The integration is on by default when tracing is enabled.

• feat(node): Stop sending the process session once request sessions are tracked (#24915)

  Node servers sent release health data two times: as request session aggregates, and as the process session of processSessionIntegration. An error in a request also marked the process session as errored, so the SDK counted the error two times. Now the SDK drops the process session when it tracks the first request session. Scripts, CLIs and workers that do not serve requests keep the process session, and so do servers with httpServerIntegration({ sessions: false }). This changes the release health numbers of Node servers, because they no longer send the errored or crashed update of the process session.

• feat(server-utils): Record decide calls as gen_ai.decide spans (#25270, #25272, #25274, #25281)

... (truncated)

Commits

• 47dff7d release: 11.7.0
• 72588e6 Merge pull request #25296 from getsentry/prepare-release/11.7.0
• 323307a meta(changelog): Update changelog for 11.7.0
• 87bdc84 fix(bundler-plugins): Escape JSON in generated injection code (#25265)
• b80300b fix(server-utils): Stop treating previous_response_id as the OpenAI conversat...
• 236c0ce fix(browser): Apply urlQueryParams to breadcrumb and element timing URLs (#...
• ee04661 fix(browser): Apply urlQueryParams to event URLs, static span names and LCP...
• 1e86178 fix(nuxt): Keep @sentry/server-runtime-injection external on Nitro v3 (#24901)
• 8a6b9ca test(node-integration): Stop exporting NODE_VERSION and RUNTIME from the ...
• 9f7cbad feat(server-utils): Map Mastra classifier evaluations to gen_ai.decide spans ...
• Additional commits viewable in compare view

[heliocosta-dev]

@dependabot rebase