Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@sentry/vue

Package Overview
Dependencies
Maintainers
11
Versions
370
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@sentry/vue - npm Package Versions

23
37

8.48.0

Diff

sentry-bot
published 8.47.0 •

sentry-bot
published 8.46.0 •

sentry-bot
published 8.45.1 •

sentry-bot
published 8.45.0 •

Changelog

Source

8.45.0

  • feat(core): Add handled option to captureConsoleIntegration (#14664)
  • feat(browser): Attach virtual stack traces to HttpClient events (#14515)
  • feat(replay): Upgrade rrweb packages to 2.31.0 (#14689)
  • fix(aws-serverless): Remove v8 layer as it overwrites the current layer for docs (#14679)
  • fix(browser): Mark stack trace from captureMessage with attachStacktrace: true as synthetic (#14668)
  • fix(core): Mark stack trace from captureMessage with attatchStackTrace: true as synthetic (#14670)
  • fix(core): Set level in server runtime captureException (#10587)
  • fix(profiling-node): Guard invocation of native profiling methods (#14676)
  • fix(nuxt): Inline nitro-utils function (#14680)
  • fix(profiling-node): Ensure profileId is added to transaction event (#14681)
  • fix(react): Add React Router Descendant Routes support (#14304)
  • fix: Disable ANR and Local Variables if debugger is enabled via CLI args (#14643)

Work in this release was contributed by @anonrig and @Zih0. Thank you for your contributions!

sentry-bot
published 7.120.2 •

sentry-bot
published 8.44.0 •

Changelog

Source

8.44.0

Deprecations

  • feat: Deprecate autoSessionTracking (#14640)

    Deprecates autoSessionTracking. To enable session tracking, it is recommended to unset autoSessionTracking and ensure that either, in browser environments the browserSessionIntegration is added, or in server environments the httpIntegration is added.

    To disable session tracking, it is recommended to unset autoSessionTracking and to remove the browserSessionIntegration in browser environments, or in server environments configure the httpIntegration with the trackIncomingRequestsAsSessions option set to false.

Other Changes

  • feat: Reword log message around unsent spans (#14641)
  • feat(opentelemetry): Set response context for http.server spans (#14634)
  • fix(google-cloud-serverless): Update homepage link in package.json (#14411)
  • fix(nuxt): Add unbuild config to not fail on warn (#14662)

Work in this release was contributed by @robinvw1. Thank you for your contribution!

sentry-bot
published 8.43.0 •

Changelog

Source

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(),
      ],
    });
    
  • 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';
    
    const featureFlagsIntegrationInstance = Sentry.featureFlagsIntegration();
    
    Sentry.init({
      // Initialize the SDK with the feature flag integration
      integrations: [featureFlagsIntegrationInstance],
    });
    
    // Manually track a feature flag
    featureFlagsIntegrationInstance.addFeatureFlag('my-feature', true);
    
  • feat(astro): Add Astro 5 support (#14613)

    With this release, the Sentry Astro SDK officially supports Astro 5.

Deprecations

  • feat(nextjs): Deprecate typedef for hideSourceMaps (#14594)

    The functionality of hideSourceMaps was removed in version 8 but was forgotten to be deprecated and removed. It will be completely removed in the next major version.

  • feat(core): Deprecate APIs around RequestSessions (#14566)

    The APIs around RequestSessions are mostly used internally. Going forward the SDK will not expose concepts around RequestSessions. Instead, functionality around server-side Release Health will be managed in integrations.

Other Changes

  • feat(browser): Add browserSessionIntegration (#14551)
  • feat(core): Add raw_security envelope types (#14562)
  • feat(deps): Bump @opentelemetry/instrumentation from 0.55.0 to 0.56.0 (#14625)
  • feat(deps): Bump @sentry/cli from 2.38.2 to 2.39.1 (#14626)
  • feat(deps): Bump @sentry/rollup-plugin from 2.22.6 to 2.22.7 (#14622)
  • feat(deps): Bump @sentry/webpack-plugin from 2.22.6 to 2.22.7 (#14623)
  • feat(nestjs): Add fastify support (#14549)
  • feat(node): Add @vercel/ai instrumentation (#13892)
  • feat(node): Add disableAnrDetectionForCallback function (#14359)
  • feat(node): Add trackIncomingRequestsAsSessions option to http integration (#14567)
  • feat(nuxt): Add option autoInjectServerSentry (no default import()) (#14553)
  • feat(nuxt): Add warning when Netlify or Vercel build is discovered (#13868)
  • feat(nuxt): Improve serverless event flushing and scope isolation (#14605)
  • feat(opentelemetry): Stop looking at propagation context for span creation (#14481)
  • feat(opentelemetry): Update OpenTelemetry dependencies to ^1.29.0 (#14590)
  • feat(opentelemetry): Update OpenTelemetry dependencies to 1.28.0 (#14547)
  • feat(replay): Upgrade rrweb packages to 2.30.0 (#14597)
  • fix(core): Decode filename and module stack frame properties in Node stack parser (#14544)
  • fix(core): Filter out unactionable CEFSharp promise rejection error by default (#14595)
  • fix(nextjs): Don't show warning about devtool option (#14552)
  • fix(nextjs): Only apply tracing metadata to data fetcher data when data is an object (#14575)
  • fix(node): Guard against invalid maxSpanWaitDuration values (#14632)
  • fix(react): Match routes with parseSearch option in TanStack Router instrumentation (#14328)
  • fix(sveltekit): Fix git SHA not being picked up for release (#14540)
  • fix(types): Fix generic exports with default (#14576)

Work in this release was contributed by @lsmurray. Thank you for your contribution!

sentry-bot
published 7.120.1 •

sentry-bot
published 8.42.0 •

Changelog

Source

8.42.0

Important Changes

Deprecations

  • feat: Warn about source-map generation (#14533)

    In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application. Currently, the implementation varies a lot between different SDKs and can be difficult to understand. Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off. Additionally, if we end up enabling source maps, we will emit a log message that we did so.

    With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.

  • feat(nuxt): Deprecate tracingOptions in favor of vueIntegration (#14530)

    Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:

    • In Sentry.init()
    • Inside tracingOptions in Sentry.init()

    For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported vueIntegration() and its tracingOptions option to configure tracing options in the Nuxt SDK:

    // sentry.client.config.ts
    import * as Sentry from '@sentry/nuxt';
    
    Sentry.init({
      // ...
      integrations: [
        Sentry.vueIntegration({
          tracingOptions: {
            trackComponents: true,
          },
        }),
      ],
    });
    

Other Changes

  • feat(browser-utils): Update web-vitals to v4.2.4 (#14439)
  • feat(nuxt): Expose vueIntegration (#14526)
  • fix(feedback): Handle css correctly in screenshot mode (#14535)
23
37
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc