Skip to content

fix(deps): update frontend non-major dependencies #1424

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

Open
wants to merge 1 commit into
base: staging
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 2, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@eslint-community/eslint-plugin-eslint-comments 4.4.1 -> 4.5.0 age adoption passing confidence
@nuxt/eslint (source) 1.1.0 -> 1.3.0 age adoption passing confidence
@nuxtjs/i18n (source) 9.3.0 -> 9.5.3 age adoption passing confidence
@nuxtjs/turnstile 0.9.12 -> 0.9.16 age adoption passing confidence
@pinia/nuxt (source) 0.10.1 -> 0.11.0 age adoption passing confidence
@sentry/bun (source) 9.5.0 -> 9.13.0 age adoption passing confidence
@sentry/nuxt (source) 9.5.0 -> 9.13.0 age adoption passing confidence
@sentry/profiling-node (source) 9.5.0 -> 9.13.0 age adoption passing confidence
@types/bun (source) 1.2.4 -> 1.2.9 age adoption passing confidence
axios (source) 1.8.2 -> 1.8.4 age adoption passing confidence
chart.js (source) 4.4.8 -> 4.4.9 age adoption passing confidence
codeceptjs (source) 3.7.2 -> 3.7.3 age adoption passing confidence
dompurify 3.2.4 -> 3.2.5 age adoption passing confidence
dotenv 16.4.7 -> 16.5.0 age adoption passing confidence
eslint-plugin-oxlint 0.15.13 -> 0.16.6 age adoption passing confidence
jsdom 26.0.0 -> 26.1.0 age adoption passing confidence
lint-staged 15.4.3 -> 15.5.1 age adoption passing confidence
marked (source) 15.0.7 -> 15.0.8 age adoption passing confidence
marked-extended-tables 2.0.0 -> 2.0.1 age adoption passing confidence
nuxt (source) 3.16.0 -> 3.16.2 age adoption passing confidence
oxlint (source) 0.15.13 -> 0.16.6 age adoption passing confidence
pinia 3.0.1 -> 3.0.2 age adoption passing confidence
pnpm (source) 10.6.1+sha512.40ee09af407fa9fbb5fbfb8e1cb40fbb74c0af0c3e10e9224d7b53c7658528615b2c92450e74cfad91e3a2dcafe3ce4050d80bda71d757756d2ce2b66213e9a3 -> 10.8.1 age adoption passing confidence
pnpm (source) 10.6.1 -> 10.8.1 age adoption passing confidence
prismjs 1.29.0 -> 1.30.0 age adoption passing confidence
sass 1.85.1 -> 1.86.3 age adoption passing confidence
swagger-typescript-api 13.0.23 -> 13.1.1 age adoption passing confidence
typescript (source) 5.8.2 -> 5.8.3 age adoption passing confidence
unplugin-vue-components 28.4.1 -> 28.5.0 age adoption passing confidence

Release Notes

eslint-community/eslint-plugin-eslint-comments (@​eslint-community/eslint-plugin-eslint-comments)

v4.5.0

Compare Source

Features
nuxt/eslint (@​nuxt/eslint)

v1.3.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.2.0

Compare Source

   🚀 Features
    View changes on GitHub
nuxt-modules/i18n (@​nuxtjs/i18n)

v9.5.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v9.5.2

Compare Source

This changelog is generated by GitHub Releases

   🐞 Bug Fixes
    View changes on GitHub

v9.5.1

Compare Source

This changelog is generated by GitHub Releases

   🐞 Bug Fixes
    View changes on GitHub

v9.5.0

Compare Source

This changelog is generated by GitHub Releases

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v9.4.0

Compare Source

This changelog is generated by GitHub Releases

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v9.3.4

Compare Source

This changelog is generated by GitHub Releases

   🐞 Bug Fixes
    View changes on GitHub

v9.3.3

Compare Source

This changelog is generated by GitHub Releases

   🐞 Bug Fixes
    View changes on GitHub

v9.3.2

Compare Source

This changelog is generated by GitHub Releases

   🐞 Bug Fixes
    View changes on GitHub

v9.3.1

Compare Source

This changelog is generated by GitHub Releases

   🐞 Bug Fixes
    View changes on GitHub
nuxt-modules/turnstile (@​nuxtjs/turnstile)

v0.9.16

Compare Source

Bug Fixes
  • remove now-unused [@ts-expect-error](https://redirect.github.com/ts-expect-error) (#​396) (7dddeea)

v0.9.15

Compare Source

Bug Fixes

v0.9.14

Compare Source

Bug Fixes

v0.9.13

Compare Source

Bug Fixes
getsentry/sentry-javascript (@​sentry/bun)

v9.13.0

Compare Source

Important Changes
  • feat(node): Add support for winston logger (#​15983)

    Sentry is adding support for structured logging. In this release we've added support for sending logs to Sentry via the winston logger to the Sentry Node SDK (and SDKs that use the Node SDK under the hood like @sentry/nestjs). The Logging APIs in the Sentry SDK are still experimental and subject to change.

    const winston = require('winston');
    const Transport = require('winston-transport');
    
    const transport = Sentry.createSentryWinstonTransport(Transport);
    
    const logger = winston.createLogger({
      transports: [transport],
    });
  • feat(core): Add wrapMcpServerWithSentry to instrument MCP servers from @modelcontextprotocol/sdk (#​16032)

    The Sentry SDK now supports instrumenting MCP servers from the @modelcontextprotocol/sdk package. Compatible with versions ^1.9.0 of the @modelcontextprotocol/sdk package.

    import { McpServer } from '@​modelcontextprotocol/sdk/server/mcp.js';
    
    // Create an MCP server
    const server = new McpServer({
      name: 'Demo',
      version: '1.0.0',
    });
    
    // Use the instrumented server in your application
    const instrumentedServer = Sentry.wrapMcpServerWithSentry(server);
  • feat(core): Move console integration into core and add to cloudflare/vercel-edge (#​16024)

    Console instrumentation has been added to @sentry/cloudflare and @sentry/nextjs Edge Runtime and is enabled by default. Now calls to the console object will be captured as breadcrumbs for those SDKs.

  • feat(bun): Support new Bun.serve APIs (#​16035)

    Bun 1.2.6 and above have a new Bun.serve API, which the Bun SDK now supports. The SDK instruments the new routes object that can be used to define routes for the server.

    Thanks to @​Jarred-Sumner for helping us get this supported!

Other Changes
  • feat(browser): Warn on duplicate browserTracingIntegration (#​16042)
  • feat(core): Allow delayed sending with offline transport (#​15937)
  • feat(deps): Bump @​sentry/webpack-plugin from 3.2.4 to 3.3.1 (#​16057)
  • feat(vue): Apply stateTransformer to attachments in Pinia Plugin (#​16034)
  • fix(core): Run beforeSendLog after we process log (#​16019)
  • fix(nextjs): Don't show turbopack warning for newer Next.js canaries (#​16065)
  • fix(nextjs): Include patch version 0 for min supported 15.3.0 (#​16026)
  • fix(node): Ensure late init works with all integrations (#​16016)
  • fix(react-router): Pass unstable_sentryVitePluginOptions to cli instance (#​16033)
  • fix(serverless-aws): Overwrite root span name with GraphQL if set (#​16010)

v9.12.0

Compare Source

v9.11.0

Compare Source

  • feat(browser): Add http.redirect_count attribute to browser.redirect span (#​15943)
  • feat(core): Add consoleLoggingIntegration for logs (#​15955)
  • feat(core): Don't truncate error messages (#​15818)
  • feat(nextjs): Add release injection in Turbopack (#​15958)
  • feat(nextjs): Record turbopack as tag (#​15928)
  • feat(nuxt): Base decision on source maps upload only on Nuxt source map settings (#​15859)
  • feat(react-router): Add sentryHandleRequest (#​15787)
  • fix(node): Use module instead of require for CJS check (#​15927)
  • fix(remix): Remove mentions of deprecated ErrorBoundary wrapper (#​15930)
  • ref(browser): Temporarily add sentry.previous_trace span attribute (#​15957)
  • ref(browser/core): Move all log flushing logic into clients (#​15831)
  • ref(core): Improve URL parsing utilities (#​15882)

Bundle size 📦

Path Size
@​sentry/browser 23.2 KB
@​sentry/browser - with treeshaking flags 23.02 KB
@​sentry/browser (incl. Tracing) 36.83 KB
@​sentry/browser (incl. Tracing, Replay) 73.99 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 67.39 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 78.66 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 91.22 KB
@​sentry/browser (incl. Feedback) 40.33 KB
@​sentry/browser (incl. sendFeedback) 27.83 KB
@​sentry/browser (incl. FeedbackAsync) 32.63 KB
@​sentry/react 25 KB
@​sentry/react (incl. Tracing) 38.75 KB
@​sentry/vue 27.41 KB
@​sentry/vue (incl. Tracing) 38.55 KB
@​sentry/svelte 23.23 KB
CDN Bundle 24.44 KB
CDN Bundle (incl. Tracing) 36.85 KB
CDN Bundle (incl. Tracing, Replay) 71.87 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 77.07 KB
CDN Bundle - uncompressed 71.24 KB
CDN Bundle (incl. Tracing) - uncompressed 108.94 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 220.23 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 232.8 KB
@​sentry/nextjs (client) 40.06 KB
@​sentry/sveltekit (client) 37.26 KB
@​sentry/node 142.88 KB
@​sentry/node - without tracing 96.08 KB
@​sentry/aws-serverless 120.43 KB

v9.10.1

Compare Source

v9.10.0

Compare Source

Important Changes
  • feat: Add support for logs

    • feat(node): Add logging public APIs to Node SDKs (#​15764)
    • feat(core): Add support for beforeSendLog (#​15814)
    • feat(core): Add support for parameterizing logs (#​15812)
    • fix: Remove critical log severity level (#​15824)

    All JavaScript SDKs other than @sentry/cloudflare and @sentry/deno now support sending logs via dedicated methods as part of Sentry's upcoming logging product.

    Logging is gated by an experimental option, _experiments.enableLogs.

    Sentry.init({
      dsn: 'PUBLIC_DSN',
      // `enableLogs` must be set to true to use the logging features
      _experiments: { enableLogs: true },
    });
    
    const { trace, debug, info, warn, error, fatal, fmt } = Sentry.logger;
    
    trace('Starting database connection', { database: 'users' });
    debug('Cache miss for user', { userId: 123 });
    error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
    fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });
    
    // Structured logging via the `fmt` helper function. When you use `fmt`, the string template and parameters are sent separately so they can be queried independently in Sentry.
    
    info(fmt(`Updated profile for user ${userId}`));
    warn(fmt(`Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}`));

    With server-side SDKs like @sentry/node, @sentry/bun or server-side of @sentry/nextjs or @sentry/sveltekit, you can do structured logging without needing the fmt helper function.

    const { info, warn } = Sentry.logger;
    
    info('User %s logged in successfully', [123]);
    warn('Failed to load user %s data', [123], { errorCode: 404 });

    To filter logs, or update them before they are sent to Sentry, you can use the _experiments.beforeSendLog option.

  • feat(browser): Add diagnoseSdkConnectivity() function to programmatically detect possible connectivity issues (#​15821)

    The diagnoseSdkConnectivity() function can be used to programmatically detect possible connectivity issues with the Sentry SDK.

    const result = await Sentry.diagnoseSdkConnectivity();

    The result will be an object with the following properties:

    • "no-client-active": There was no active client when the function was called. This possibly means that the SDK was not initialized yet.
    • "sentry-unreachable": The Sentry SaaS servers were not reachable. This likely means that there is an ad blocker active on the page or that there are other connection issues.
    • undefined: The SDK is working as expected.
  • SDK Tracing Performance Improvements for Node SDKs

    • feat: Stop using dropUndefinedKeys (#​15796)
    • feat(node): Only add span listeners for instrumentation when used (#​15802)
    • ref: Avoid dropUndefinedKeys for spanToJSON calls (#​15792)
    • ref: Avoid using SentryError for PromiseBuffer control flow (#​15822)
    • ref: Stop using dropUndefinedKeys in SpanExporter (#​15794)
    • ref(core): Avoid using SentryError for event processing control flow (#​15823)
    • ref(node): Avoid dropUndefinedKeys in Node SDK init (#​15797)
    • ref(opentelemetry): Avoid sampling work for non-root spans (#​15820)

    We've been hard at work making performance improvements to the Sentry Node SDKs (@sentry/node, @sentry/aws-serverless, @sentry/nestjs, etc.). We've seen that upgrading from 9.7.0 to 9.10.0 leads to 30-40% improvement in request latency for HTTP web-server applications that use tracing with high sample rates. Non web-server applications and non-tracing applications will see smaller improvements.

Other Changes
  • chore(deps): Bump rrweb to 2.35.0 (#​15825)
  • deps: Bump bundler plugins to 3.2.3 (#​15829)
  • feat: Always truncate stored breadcrumb messages to 2kb (#​15819)
  • feat(nextjs): Disable server webpack-handling for static builds (#​15751)
  • fix(nuxt): Don't override Nuxt options if undefined (#​15795)

v9.9.0

Compare Source

Important Changes
  • feat(nextjs): Support instrumentation-client.ts (#​15705)

    Next.js recently added a feature to support client-side (browser) instrumentation via the experimental.clientInstrumentationHook flag and the instrumentation-client.ts file.

    To be forwards compatible, the Sentry Next.js SDK will now pick up instrumentation-client.ts files even on older Next.js versions and add them to your client bundles.
    It is suggested that you either rename your sentry.client.config.ts file to instrumentation-client.ts, or if you already happen to have a instrumentation-client.ts file move the contents of sentry.client.config.ts to instrumentation-client.ts.

  • feat(browser): Add previous_trace span links (#​15569)

    The @sentry/browser SDK and SDKs based on @sentry/browser now emits a link from the first root span of a newly started trace to the root span of a previously started trace. You can control this feature via an option in browserTracingIntegration():

    Sentry.init({
      dsn: 'your-dsn-here'
      integrations: [
        Sentry.browserTracingIntegration({
          // Available settings:
          // - 'in-memory' (default): Stores previous trace information in memory
          // - 'session-storage': Stores previous trace information in the browser's `sessionStorage`
          // - 'off': Disable storing and sending previous trace information
          linkPreviousTrace: 'in-memory',
        }),
      ],
    });
  • feat(browser): Add logger.X methods to browser SDK (#​15763)

    For Sentry's upcoming logging product, the SDK now supports sending logs via dedicated methods.

    Sentry.init({
      dsn: 'your-dsn-here',
      _experiments: {
        enableLogs: true, // This is required to use the logging features
      },
    });
    
    Sentry.logger.info('This is a trace message', { userId: 123 });
    // See PR for better documentation

    Please note that the logs product is still in early access. See the link above for more information.

Other Changes
  • feat(browser): Attach host as part of error message to "Failed to fetch" errors (#​15729)
  • feat(core): Add parseStringToURL method (#​15768)
  • feat(core): Optimize dropUndefinedKeys (#​15760)
  • feat(node): Add fastify shouldHandleError (#​15771)
  • fix(nuxt): Delete no longer needed Nitro 'close' hook (#​15790)
  • perf(nestjs): Remove usage of addNonEnumerableProperty (#​15766)
  • ref: Avoid some usage of dropUndefinedKeys() (#​15757)
  • ref: Remove some usages of dropUndefinedKeys() (#​15781)
  • ref(nextjs): Fix Next.js vercel-edge runtime package information (#​15789)

v9.8.0

Compare Source

  • feat(node): Implement new continuous profiling API spec (#​15635)
  • feat(profiling): Add platform to chunk envelope (#​15758)
  • feat(react): Export captureReactException method (#​15746)
  • fix(node): Check for res.end before passing to Proxy (#​15776)
  • perf(core): Add short-circuits to eventFilters integration (#​15752)
  • perf(node): Short circuit flushing on Vercel only for Vercel (#​15734)

v9.7.0

Compare Source

  • feat(core): Add captureLog method (#​15717)
  • feat(remix/cloudflare): Export sentryHandleError (#​15726)
  • fix(node): Always flush on Vercel before Lambda freeze (#​15602)
  • fix(node): Ensure incoming traces are propagated without HttpInstrumentation ([#&

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate renovate bot force-pushed the renovate/frontend-minor-patch branch 14 times, most recently from d1ac7f7 to 48a3d15 Compare December 6, 2024 16:05
@renovate renovate bot force-pushed the renovate/frontend-minor-patch branch 2 times, most recently from daa8787 to 148dec7 Compare December 10, 2024 13:49
@renovate renovate bot changed the title chore(deps): update frontend non-major dependencies fix(deps): update frontend non-major dependencies Dec 10, 2024
@renovate renovate bot force-pushed the renovate/frontend-minor-patch branch 13 times, most recently from 0d77c73 to 4cda40b Compare December 16, 2024 06:40
@renovate renovate bot force-pushed the renovate/frontend-minor-patch branch 9 times, most recently from d64162f to cac17b8 Compare April 3, 2025 15:37
@renovate renovate bot force-pushed the renovate/frontend-minor-patch branch 11 times, most recently from 5be64dd to 375bfb6 Compare April 11, 2025 03:06
@renovate renovate bot force-pushed the renovate/frontend-minor-patch branch 8 times, most recently from 9f2ecad to 1722f5f Compare April 15, 2025 17:03
@renovate renovate bot force-pushed the renovate/frontend-minor-patch branch from 1722f5f to 3d3d147 Compare April 16, 2025 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants