Charly Gomez

@Jonatthu @bephrem1 we're aware of this, there is is an open upstream issue for that: https://github.com/oven-sh/bun/issues/13165

@Rakhymbek additionally I also noticed that in your dockerfile you are using `yarn install` but keep referencing `package-lock.json`. Setting this to `yarn.lock` did result in a successful build with the...

@Rakhymbek disabling `instrumentationHook` will basically disable all server-side instrumentation for your next.js app, you want to keep that to `true` and initialize sentry in the `instrumentation.ts` file

@Rakhymbek Yes, if you need server-side performance instrumentation you will need to keep `instrumentationHook: true`

@Rakhymbek if the domain is not available, by default an error will be thrown. You can however handle build errors in your `withSentryConfig` via: ```js unstable_sentryWebpackPluginOptions: { errorHandler: // handle...

Good to hear! I think the only documentation for that is probably [here](https://www.npmjs.com/package/@sentry/webpack-plugin#errorhandler) – this should also be available in v7.

@mikan3rd Did you try running your Apollo server without manually continuing the trace, or is there a specific reason for the code inside your `context` function?

closed by https://github.com/getsentry/sentry-javascript/pull/14549

Hey @SarathSantoshDamaraju thanks for writing in. Are you using the same SDK version across your microfrontends? To solve your issue more effectively could you please provide your `init` call of...

@SarathSantoshDamaraju I got your code snippet from our support team. Some things to mention: - In your `beforeSend` callback of your host app you need to return the event at...