Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency @sentry/nextjs to v8 #2985

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 13, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sentry/nextjs (source) 7.120.1 -> 8.42.0 age adoption passing confidence

Release Notes

getsentry/sentry-javascript (@​sentry/nextjs)

v8.42.0

Compare Source

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)

Bundle size 📦

Path Size
@​sentry/browser 23.1 KB
@​sentry/browser - with treeshaking flags 21.84 KB
@​sentry/browser (incl. Tracing) 35.61 KB
@​sentry/browser (incl. Tracing, Replay) 72.47 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 62.96 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 76.79 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 89.28 KB
@​sentry/browser (incl. Feedback) 39.86 KB
@​sentry/browser (incl. sendFeedback) 27.72 KB
@​sentry/browser (incl. FeedbackAsync) 32.53 KB
@​sentry/react 25.8 KB
@​sentry/react (incl. Tracing) 38.49 KB
@​sentry/vue 27.25 KB
@​sentry/vue (incl. Tracing) 37.38 KB
@​sentry/svelte 23.25 KB
CDN Bundle 24.32 KB
CDN Bundle (incl. Tracing) 37.29 KB
CDN Bundle (incl. Tracing, Replay) 72.15 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 77.49 KB
CDN Bundle - uncompressed 71.45 KB
CDN Bundle (incl. Tracing) - uncompressed 110.76 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 223.83 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 237.05 KB
@​sentry/nextjs (client) 38.78 KB
@​sentry/sveltekit (client) 36.14 KB
@​sentry/node 135.08 KB
@​sentry/node - without tracing 97.13 KB
@​sentry/aws-serverless 109.43 KB

v8.41.0

Compare Source

Important Changes
  • meta(nuxt): Require minimum Nuxt v3.7.0 (#​14473)

    We formalized that the Nuxt SDK is at minimum compatible with Nuxt version 3.7.0 and above.
    Additionally, the SDK requires the implicit nitropack dependency to satisfy version ^2.10.0 and ofetch to satisfy ^1.4.0.
    It is recommended to check your lock-files and manually upgrade these dependencies if they don't match the version ranges.

Deprecations

We are deprecating a few APIs which will be removed in the next major.

The following deprecations will potentially affect you:

  • feat(core): Update & deprecate undefined option handling (#​14450)

    In the next major version we will change how passing undefined to tracesSampleRate / tracesSampler / enableTracing will behave.

    Currently, doing the following:

    Sentry.init({
      tracesSampleRate: undefined,
    });

    Will result in tracing being enabled (although no spans will be generated) because the tracesSampleRate key is present in the options object.
    In the next major version, this behavior will be changed so that passing undefined (or rather having a tracesSampleRate key) will result in tracing being disabled, the same as not passing the option at all.
    If you are currently relying on undefined being passed, and and thus have tracing enabled, it is recommended to update your config to set e.g. tracesSampleRate: 0 instead, which will also enable tracing in v9.

    The same applies to tracesSampler and enableTracing.

  • feat(core): Log warnings when returning null in beforeSendSpan (#​14433)

    Currently, the beforeSendSpan option in Sentry.init() allows you to drop individual spans from a trace by returning null from the hook.
    Since this API lends itself to creating "gaps" inside traces, we decided to change how this API will work in the next major version.

    With the next major version the beforeSendSpan API can only be used to mutate spans, but no longer to drop them.
    With this release the SDK will warn you if you are using this API to drop spans.
    Instead, it is recommended to configure instrumentation (i.e. integrations) directly to control what spans are created.

    Additionally, with the next major version, root spans will also be passed to beforeSendSpan.

  • feat(utils): Deprecate @sentry/utils (#​14431)

    With the next major version the @sentry/utils package will be merged into the @sentry/core package.
    It is therefore no longer recommended to use the @sentry/utils package.

  • feat(vue): Deprecate configuring Vue tracing options anywhere else other than through the vueIntegration's tracingOptions option (#​14385)

    Currently it is possible to configure tracing options in various places in the Sentry Vue SDK:

    • In Sentry.init()
    • Inside tracingOptions in Sentry.init()
    • In the vueIntegration() options
    • Inside tracingOptions in the vueIntegration() options

    Because this is a bit messy and confusing to document, the only recommended way to configure tracing options going forward is through the tracingOptions in the vueIntegration().
    The other means of configuration will be removed in the next major version of the SDK.

  • feat: Deprecate registerEsmLoaderHooks.include and registerEsmLoaderHooks.exclude (#​14486)

    Currently it is possible to define registerEsmLoaderHooks.include and registerEsmLoaderHooks.exclude options in Sentry.init() to only apply ESM loader hooks to a subset of modules.
    This API served as an escape hatch in case certain modules are incompatible with ESM loader hooks.

    Since this API was introduced, a way was found to only wrap modules that there exists instrumentation for (meaning a vetted list).
    To only wrap modules that have instrumentation, it is recommended to instead set registerEsmLoaderHooks.onlyIncludeInstrumentedModules to true.

    Note that onlyIncludeInstrumentedModules: true will become the default behavior in the next major version and the registerEsmLoaderHooks will no longer accept fine-grained options.

The following deprecations will most likely not affect you unless you are building an SDK yourself:

  • feat(core): Deprecate arrayify (#​14405)
  • feat(core): Deprecate flatten (#​14454)
  • feat(core): Deprecate urlEncode (#​14406)
  • feat(core): Deprecate validSeverityLevels (#​14407)
  • feat(core/utils): Deprecate getNumberOfUrlSegments (#​14458)
  • feat(utils): Deprecate memoBuilder, BAGGAGE_HEADER_NAME, and makeFifoCache (#​14434)
  • feat(utils/core): Deprecate addRequestDataToEvent and extractRequestData (#​14430)
Other Changes
  • feat: Streamline sentry-trace, baggage and DSC handling (#​14364)
  • feat(core): Further optimize debug ID parsing (#​14365)
  • feat(node): Add openTelemetryInstrumentations option (#​14484)
  • feat(nuxt): Add filter for not found source maps (devtools) (#​14437)
  • feat(nuxt): Only delete public source maps (#​14438)
  • fix(nextjs): Don't report NEXT_REDIRECT from browser (#​14440)
  • perf(opentelemetry): Bucket spans for cleanup (#​14154)

Work in this release was contributed by @​NEKOYASAN and @​fmorett. Thank you for your contributions!

Bundle size 📦

Path Size
@​sentry/browser 23.12 KB
@​sentry/browser - with treeshaking flags 21.84 KB
@​sentry/browser (incl. Tracing) 35.53 KB
@​sentry/browser (incl. Tracing, Replay) 72.44 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 62.81 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 76.76 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 89.21 KB
@​sentry/browser (incl. Feedback) 39.86 KB
@​sentry/browser (incl. sendFeedback) 27.73 KB
@​sentry/browser (incl. FeedbackAsync) 32.53 KB
@​sentry/react 25.8 KB
@​sentry/react (incl. Tracing) 38.36 KB
@​sentry/vue 27.28 KB
@​sentry/vue (incl. Tracing) 37.33 KB
@​sentry/svelte 23.27 KB
CDN Bundle 24.29 KB
CDN Bundle (incl. Tracing) 37.17 KB
CDN Bundle (incl. Tracing, Replay) 72.06 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 77.41 KB
CDN Bundle - uncompressed 71.37 KB
CDN Bundle (incl. Tracing) - uncompressed 110.4 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 223.47 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 236.69 KB
@​sentry/nextjs (client) 38.68 KB
@​sentry/sveltekit (client) 36.05 KB
@​sentry/node 135.06 KB
@​sentry/node - without tracing 96.89 KB
@​sentry/aws-serverless 107.09 KB

v8.40.0

Compare Source

Important Changes
  • feat(angular): Support Angular 19 (#​14398)

    The @sentry/angular SDK can now be used with Angular 19. If you're upgrading to the new Angular version, you might want to migrate from the now deprecated APP_INITIALIZER token to provideAppInitializer.
    In this case, change the Sentry TraceService initialization in app.config.ts:

    // Angular 18
    export const appConfig: ApplicationConfig = {
      providers: [
        // other providers
        {
          provide: TraceService,
          deps: [Router],
        },
        {
          provide: APP_INITIALIZER,
          useFactory: () => () => {},
          deps: [TraceService],
          multi: true,
        },
      ],
    };
    
    // Angular 19
    export const appConfig: ApplicationConfig = {
      providers: [
        // other providers
        {
          provide: TraceService,
          deps: [Router],
        },
        provideAppInitializer(() => {
          inject(TraceService);
        }),
      ],
    };
  • feat(core): Deprecate debugIntegration and sessionTimingIntegration (#​14363)

    The debugIntegration was deprecated and will be removed in the next major version of the SDK.
    To log outgoing events, use Hook Options (beforeSend, beforeSendTransaction, ...).

    The sessionTimingIntegration was deprecated and will be removed in the next major version of the SDK.
    To capture session durations alongside events, use Context (Sentry.setContext()).

  • feat(nestjs): Deprecate @WithSentry in favor of @SentryExceptionCaptured (#​14323)

    The @WithSentry decorator was deprecated. Use @SentryExceptionCaptured instead. This is a simple renaming and functionality stays identical.

  • feat(nestjs): Deprecate SentryTracingInterceptor, SentryService, SentryGlobalGenericFilter, SentryGlobalGraphQLFilter (#​14371)

    The SentryTracingInterceptor was deprecated. If you are using @sentry/nestjs you can safely remove any references to the SentryTracingInterceptor. If you are using another package migrate to @sentry/nestjs and remove the SentryTracingInterceptor afterwards.

    The SentryService was deprecated and its functionality was added to Sentry.init. If you are using @sentry/nestjs you can safely remove any references to the SentryService. If you are using another package migrate to @sentry/nestjs and remove the SentryService afterwards.

    The SentryGlobalGenericFilter was deprecated. Use the SentryGlobalFilter instead which is a drop-in replacement.

    The SentryGlobalGraphQLFilter was deprecated. Use the SentryGlobalFilter instead which is a drop-in replacement.

  • feat(node): Deprecate nestIntegration and setupNestErrorHandler in favor of using @sentry/nestjs (#​14374)

    The nestIntegration and setupNestErrorHandler functions from @sentry/node were deprecated and will be removed in the next major version of the SDK. If you're using @sentry/node in a NestJS application, we recommend switching to our new dedicated @sentry/nestjs package.

Other Changes
  • feat(browser): Send additional LCP timing info (#​14372)
  • feat(replay): Clear event buffer when full and in buffer mode (#​14078)
  • feat(core): Ensure normalizedRequest on sdkProcessingMetadata is merged (#​14315)
  • feat(core): Hoist everything from @sentry/utils into @sentry/core (#​14382)
  • fix(core): Do not throw when trying to fill readonly properties (#​14402)
  • fix(feedback): Fix __self and __source attributes on feedback nodes (#​14356)
  • fix(feedback): Fix non-wrapping form title (#​14355)
  • fix(nextjs): Update check for not found navigation error (#​14378)

Bundle size 📦

Path Size
@​sentry/browser 22.88 KB
@​sentry/browser - with treeshaking flags 21.57 KB
@​sentry/browser (incl. Tracing) 35.46 KB
@​sentry/browser (incl. Tracing, Replay) 72.22 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 62.53 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 76.52 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 89.02 KB
@​sentry/browser (incl. Feedback) 39.63 KB
@​sentry/browser (incl. sendFeedback) 27.51 KB
@​sentry/browser (incl. FeedbackAsync) 32.32 KB
@​sentry/react 25.58 KB
@​sentry/react (incl. Tracing) 38.32 KB
@​sentry/vue 27.04 KB
@​sentry/vue (incl. Tracing) 37.27 KB
@​sentry/svelte 23.03 KB
CDN Bundle 24.04 KB
CDN Bundle (incl. Tracing) 37.02 KB
CDN Bundle (incl. Tracing, Replay) 71.81 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 77.16 KB
CDN Bundle - uncompressed 70.9 KB
CDN Bundle (incl. Tracing) - uncompressed 110.25 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 223.05 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 236.27 KB
@​sentry/nextjs (client) 38.42 KB
@​sentry/sveltekit (client) 35.97 KB
@​sentry/node 134.48 KB
@​sentry/node - without tracing 96.32 KB
@​sentry/aws-serverless 106.57 KB

v8.39.0

Compare Source

Important Changes
  • feat(nestjs): Instrument event handlers (#​14307)

The @sentry/nestjs SDK will now capture performance data for NestJS Events (@nestjs/event-emitter)

Other Changes
  • feat(nestjs): Add alias @SentryExceptionCaptured for @WithSentry (#​14322)
  • feat(nestjs): Duplicate SentryService behaviour into @sentry/nestjs SDK init() (#​14321)
  • feat(nestjs): Handle GraphQL contexts in SentryGlobalFilter (#​14320)
  • feat(node): Add alias childProcessIntegration for processThreadBreadcrumbIntegration and deprecate it (#​14334)
  • feat(node): Ensure request bodies are reliably captured for http requests (#​13746)
  • feat(replay): Upgrade rrweb packages to 2.29.0 (#​14160)
  • fix(cdn): Ensure _sentryModuleMetadata is not mangled (#​14344)
  • fix(core): Set sentry.source attribute to custom when calling span.updateName on SentrySpan (#​14251)
  • fix(mongo): rewrite Buffer as ? during serialization (#​14071)
  • fix(replay): Remove replay id from DSC on expired sessions (#​14342)
  • ref(profiling) Fix electron crash (#​14216)
  • ref(types): Deprecate Request type in favor of RequestEventData (#​14317)
  • ref(utils): Stop setting transaction in requestDataIntegration (#​14306)
  • ref(vue): Reduce bundle size for starting application render span (#​14275)

Bundle size 📦

Path Size
@​sentry/browser 22.77 KB
@​sentry/browser - with treeshaking flags 21.53 KB
@​sentry/browser (incl. Tracing) 35.27 KB
@​sentry/browser (incl. Tracing, Replay) 72 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 62.38 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 76.31 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 89.17 KB
@​sentry/browser (incl. Feedback) 39.93 KB
@​sentry/browser (incl. sendFeedback) 27.42 KB
@​sentry/browser (incl. FeedbackAsync) 32.23 KB
@​sentry/react 25.52 KB
@​sentry/react (incl. Tracing) 38.23 KB
@​sentry/vue 26.92 KB
@​sentry/vue (incl. Tracing) 37.1 KB
@​sentry/svelte 22.91 KB
CDN Bundle 24.13 KB
CDN Bundle (incl. Tracing) 37.05 KB
CDN Bundle (incl. Tracing, Replay) 71.72 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 77.07 KB
CDN Bundle - uncompressed 70.73 KB
CDN Bundle (incl. Tracing) - uncompressed 109.94 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 222.46 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 235.68 KB
@​sentry/nextjs (client) 38.35 KB
@​sentry/sveltekit (client) 35.85 KB
@​sentry/node 134.33 KB
@​sentry/node - without tracing 96.2 KB
@​sentry/aws-serverless 106.48 KB

v8.38.0

Compare Source

  • docs: Improve docstrings for node otel integrations (#​14217)
  • feat(browser): Add moduleMetadataIntegration lazy loading support (#​13817)
  • feat(core): Add trpc path to context in trpcMiddleware (#​14218)
  • feat(deps): Bump @​opentelemetry/instrumentation-amqplib from 0.42.0 to 0.43.0 (#​14230)
  • feat(deps): Bump @​sentry/cli from 2.37.0 to 2.38.2 (#​14232)
  • feat(node): Add knex integration (#​13526)
  • feat(node): Add tedious integration (#​13486)
  • feat(utils): Single implementation to fetch debug ids (#​14199)
  • fix(browser): Avoid recording long animation frame spans starting before their parent span (#​14186)
  • fix(node): Include debug_meta with ANR events (#​14203)
  • fix(nuxt): Fix dynamic import rollup plugin to work with latest nitro (#​14243)
  • fix(react): Support wildcard routes on React Router 6 (#​14205)
  • fix(spotlight): Export spotlightBrowserIntegration from the main browser package (#​14208)
  • ref(browser): Ensure start time of interaction root and child span is aligned (#​14188)
  • ref(nextjs): Make build-time value injection turbopack compatible (#​14081)

Work in this release was contributed by @​grahamhency, @​Zen-cronic, @​gilisho and @​phuctm97. Thank you for your contributions!

v8.37.1

Compare Source

v8.37.0

Compare Source

Important Changes
  • feat(nuxt): Add piniaIntegration (#​14138)

The Nuxt SDK now allows you to track Pinia state for captured errors. To enable the Pinia plugin, add the piniaIntegration to your client config:

// sentry.client.config.ts
import { usePinia } from '#imports';

Sentry.init({
  integrations: [
    Sentry.piniaIntegration(usePinia(), {
      /* optional Pinia plugin options */
    }),
  ],
});

The Sentry Metrics beta has ended in favour of revisiting metrics in another form at a later date.

This new approach will include different APIs, making the current metrics API unnecessary. This release
deprecates the metrics API with the plan to remove in the next SDK major version. If you currently use the
metrics API in your code, you can safely continue to do so but sent data will no longer be processed by Sentry.

Learn more about the end of the Metrics beta.

Other Changes

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

v8.36.0

Compare Source

Important Changes
  • feat(nuxt): Add Sentry Pinia plugin (#​14047)

The Nuxt SDK now allows you to track Pinia state for captured errors. To enable the Pinia plugin, set the trackPinia option to true in your client config:

// sentry.client.config.ts

Sentry.init({
  trackPinia: true,
});

Read more about the Pinia plugin in the Sentry Pinia Documentation.

  • feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#​13889)

With this release, the Sentry Next.js, and Cloudflare SDKs will now capture performance data based on OpenTelemetry.
Some exceptions apply in cases where Next.js captures inaccurate data itself.

NOTE: You may experience minor differences in transaction names in Sentry.
Most importantly transactions for serverside pages router invocations will now be named GET /[param]/my/route instead of /[param]/my/route.
This means that those transactions are now better aligned with the OpenTelemetry semantic conventions.

Other Changes

v8.35.0

Compare Source

v8.34.0

Compare Source

Important Changes

Relevant for users of the @sentry/nextjs package: If you have previously configured a
SENTRY_IGNORE_API_RESOLUTION_ERROR environment variable, it is now safe to unset it.

Other Changes
  • feat(cdn): Export getReplay in replay CDN bundles
    (#​13881)
  • feat(replay): Clear fallback buffer when switching buffers
    (#​13914)
  • feat(replay): Upgrade rrweb packages to 2.28.0 (#​13732)
  • fix(docs): Correct supported browsers due to globalThis
    (#​13788)
  • fix(nextjs): Adjust path to requestAsyncStorageShim.js template file
    (#​13928)
  • fix(nextjs): Detect new locations for request async storage to support Next.js v15.0.0-canary.180 and higher
    (#​13920)
  • fix(nextjs): Drop _not-found spans for all HTTP methods
    (#​13906)
  • fix(nextjs): Fix resolution of request storage shim fallback
    (#​13929)
  • fix(node): Ensure graphql options are correct when preloading
    (#​13769)
  • fix(node): Local variables handle error (#​13827)
  • fix(node): Remove dataloader instrumentation from default integrations
    (#​13873)
  • fix(nuxt): Create declaration files for Nuxt module
    (#​13909)
  • fix(replay): Ensure replay_id is removed from frozen DSC when stopped
    (#​13893)
  • fix(replay): Try/catch sendBufferedReplayOrFlush to prevent cycles
    (#​13900)
  • fix(sveltekit): Ensure trace meta tags are always injected
    (#​13231)
  • fix(sveltekit): Update wrapServerRouteWithSentry to respect ParamMatchers
    (#​13390)
  • fix(wasm): Integration wasm uncaught WebAssembly.Exception
    (#​13787) (#​13854)
  • ref(nextjs): Ignore sentry spans based on query param attribute
    (#​13905)
  • ref(utils): Move vercelWaitUntil to utils (#​13891)

Work in this release was contributed by @​trzeciak, @​gurpreetatwal, @​ykzts and @​lizhiyao. Thank you for your
contributions!

Bundle size 📦

Path Size
@​sentry/browser 22.73 KB
@​sentry/browser - with treeshaking flags 21.53 KB
@​sentry/browser (incl. Tracing) 34.97 KB
@​sentry/browser (incl. Tracing, Replay) 71.62 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 62.03 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 75.97 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 88.73 KB
@​sentry/browser (incl. Tracing, Replay, Feedback, metrics) 90.59 KB
@​sentry/browser (incl. metrics) 27 KB
@​sentry/browser (incl. Feedback) 39.87 KB
@​sentry/browser (incl. sendFeedback) 27.38 KB
@​sentry/browser (incl. FeedbackAsync) 32.17 KB
@​sentry/react 25.49 KB
@​sentry/react (incl. Tracing) 37.94 KB
@​sentry/vue 26.91 KB
@​sentry/vue (incl. Tracing) 36.86 KB
@​sentry/svelte 22.87 KB
CDN Bundle 24.05 KB
CDN Bundle (incl. Tracing) 36.76 KB
CDN Bundle (incl. Tracing, Replay) 71.38 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 76.7 KB
CDN Bundle - uncompressed 70.53 KB
CDN Bundle (incl. Tracing) - uncompressed 109.04 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 221.4 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 234.62 KB
@​sentry/nextjs (client) 37.91 KB
@​sentry/sveltekit (client) 35.56 KB
@​sentry/node 124.5 KB
@​sentry/node - without tracing 93.64 KB
@​sentry/aws-serverless 103.3 KB

v8.33.1

Compare Source

  • fix(core): Update trpc middleware types (#​13859)
  • fix(fetch): Fix memory leak when handling endless streaming
    (#​13809)

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

v8.33.0

Compare Source

Important Changes
  • feat(nextjs): Support new async APIs (headers(), params, searchParams)
    (#​13828)

Adds support for new dynamic Next.js APIs.

  • feat(node): Add lru-memoizer instrumentation
    (#​13796)

Adds integration for lru-memoizer using @​opentelemetry/instrumentation-lru-memoizer.

  • feat(nuxt): Add unstable_sentryBundlerPluginOptions to module options
    (#​13811)

Allows passing other options from the bundler plugins (vite and rollup) to Nuxt module options.

Other Changes
  • fix(browser): Ensure wrap() only returns functions
    (#​13838)
  • fix(core): Adapt trpc middleware input attachment
    (#​13831)
  • fix(core): Don't return trace data in getTraceData and getTraceMetaTags if SDK is disabled
    (#​13760)
  • fix(nuxt): Don't restrict source map assets upload
    (#​13800)
  • fix(nuxt): Use absolute path for client config (#​13798)
  • fix(replay): Stop global event handling for paused replays
    (#​13815)
  • fix(sveltekit): add url param to source map upload options
    (#​13812)
  • fix(types): Add jsdocs to cron types (#​13776)
  • fix(nextjs): Loosen @​sentry/nextjs webpack peer dependency
    (#​13826)

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

Bundle size 📦
Path Size
@​sentry/browser 22.64 KB
@​sentry/browser - with treeshaking flags 21.42 KB
@​sentry/browser (incl. Tracing) 34.87 KB
@​sentry/browser (incl. Tracing, Replay) 71.37 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 61.8 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 75.72 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 88.49 KB
@​sentry/browser (incl. Tracing, Replay, Feedback, metrics) 90.37 KB
@​sentry/browser (incl. metrics) 26.91 KB
@​sentry/browser (incl. Feedback) 39.78 KB
@​sentry/browser (incl. sendFeedback) 27.3 KB
@​sentry/browser (incl. FeedbackAsync) 32.08 KB
@​sentry/react 25.39 KB
@​sentry/react (incl. Tracing) 37.85 KB
@​sentry/vue 26.8 KB
@​sentry/vue (incl. Tracing) 36.76 KB
@​sentry/svelte 22.77 KB
CDN Bundle 23.95 KB
CDN Bundle (incl. Tracing) 36.64 KB
CDN Bundle (incl. Tracing, Replay)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

socket-security bot commented May 13, 2024

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Possible typosquat attack npm/@nolyfill/[email protected] ⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

@renovate renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch 18 times, most recently from 30b141a to 5e4cbdd Compare May 16, 2024 14:13
@Mintoo200 Mintoo200 force-pushed the renovate/major-sentry-javascript-monorepo branch from 6b8b314 to dc8c02d Compare May 16, 2024 15:52
@Mintoo200
Copy link
Contributor

@SocketSecurity ignore npm/@sentry/[email protected]

@Mintoo200 Mintoo200 force-pushed the renovate/major-sentry-javascript-monorepo branch from dc8c02d to 6cd866f Compare May 16, 2024 15:57
@Mintoo200
Copy link
Contributor

@Mintoo200 Mintoo200 added blocked and removed blocked labels May 17, 2024
@renovate renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from cb3358c to fabfa4a Compare July 16, 2024 09:25
@Mintoo200 Mintoo200 force-pushed the renovate/major-sentry-javascript-monorepo branch from fabfa4a to 6cd866f Compare July 16, 2024 09:35
@renovate renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 6cd866f to ac32fb6 Compare July 16, 2024 09:39
@renovate renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch 19 times, most recently from 8ed14a0 to 5ca5584 Compare December 3, 2024 22:14
@renovate renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch 6 times, most recently from 0c97d2b to c523091 Compare December 5, 2024 08:39
@renovate renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from c523091 to fefb318 Compare December 5, 2024 11:01
@sokl-octo sokl-octo closed this Dec 6, 2024
Copy link
Contributor Author

renovate bot commented Dec 6, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 8.x releases. But if you manually upgrade to 8.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/major-sentry-javascript-monorepo branch December 6, 2024 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants