deps: bump @sentry/profiling-node from 8.42.0 to 8.43.0

[dependabot]

Bumps @sentry/profiling-node from 8.42.0 to 8.43.0.

Release notes

Sourced from @​sentry/profiling-node's releases.

8.43.0

Important Changes

• feat(nuxt): Add option autoInjectServerSentry (no default import()) (#14553)

  Using the dynamic import() as the default behavior for initializing the SDK on the server-side did not work for every project. The default behavior of the SDK has been changed, and you now need to use the --import flag to initialize Sentry on the server-side to leverage full functionality.

  Example with --import:

  node --import ./.output/server/sentry.server.config.mjs .output/server/index.mjs

  In case you are not able to use the --import flag, you can enable auto-injecting Sentry in the nuxt.config.ts (comes with limitations):

  sentry: {
    autoInjectServerSentry: 'top-level-import', // or 'experimental_dynamic-import'
  },

• feat(browser): Adds LaunchDarkly and OpenFeature integrations (#14207)

  Adds browser SDK integrations for tracking feature flag evaluations through the LaunchDarkly JS SDK and OpenFeature Web SDK:

  import * as Sentry from '@sentry/browser';
  Sentry.init({
  integrations: [
  // Track LaunchDarkly feature flags
  Sentry.launchDarklyIntegration(),
  // Track OpenFeature feature flags
  Sentry.openFeatureIntegration(),
  ],
  });

  • Read more about the Feature Flags feature in Sentry.
  • Read more about the LaunchDarkly SDK Integration.
  • Read more about the OpenFeature SDK Integration.

• feat(browser): Add featureFlagsIntegration for custom tracking of flag evaluations (#14582)

  Adds a browser integration to manually track feature flags with an API. Feature flags are attached to subsequent error events:

  import * as Sentry from '@sentry/browser';

... (truncated)

Changelog

Sourced from @​sentry/profiling-node's changelog.

8.43.0

Important Changes

• feat(nuxt): Add option autoInjectServerSentry (no default import()) (#14553)

  Using the dynamic import() as the default behavior for initializing the SDK on the server-side did not work for every project. The default behavior of the SDK has been changed, and you now need to use the --import flag to initialize Sentry on the server-side to leverage full functionality.

  Example with --import:

  node --import ./.output/server/sentry.server.config.mjs .output/server/index.mjs

  In case you are not able to use the --import flag, you can enable auto-injecting Sentry in the nuxt.config.ts (comes with limitations):

  sentry: {
    autoInjectServerSentry: 'top-level-import', // or 'experimental_dynamic-import'
  },

• feat(browser): Adds LaunchDarkly and OpenFeature integrations (#14207)

  Adds browser SDK integrations for tracking feature flag evaluations through the LaunchDarkly JS SDK and OpenFeature Web SDK:

  import * as Sentry from '@sentry/browser';
  Sentry.init({
  integrations: [
  // Track LaunchDarkly feature flags
  Sentry.launchDarklyIntegration(),
  // Track OpenFeature feature flags
  Sentry.openFeatureIntegration(),
  ],
  });

  • Read more about the Feature Flags feature in Sentry.
  • Read more about the LaunchDarkly SDK Integration.
  • Read more about the OpenFeature SDK Integration.

• feat(browser): Add featureFlagsIntegration for custom tracking of flag evaluations (#14582)

  Adds a browser integration to manually track feature flags with an API. Feature flags are attached to subsequent error events:

  import * as Sentry from '@sentry/browser';

... (truncated)

Commits

• 88ab7ce release: 8.43.0
• 177e5d1 Merge pull request #14639 from getsentry/prepare-release/8.43.0
• 5be252c meta(changelog): Update changelog for 8.43.0
• a9dcdb8 test: Skip double installing playwright in E2E tests (#14633)
• a9cfd11 fix(node): Guard against invalid maxSpanWaitDuration values (#14632)
• f962eef feat(deps): Bump @​opentelemetry/instrumentation from 0.55.0 to 0.56.0 (#14625)
• 4df242d feat(deps): Bump @​sentry/rollup-plugin from 2.22.6 to 2.22.7 (#14622)
• a5a4e8c feat(deps): Bump @​sentry/webpack-plugin from 2.22.6 to 2.22.7 (#14623)
• 242ed75 fix(core): Filter out unactionable CEFSharp promise rejection error by defaul...
• 7f0bd25 feat(astro): Add Astro 5 support (#14613)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)