Luca Forstner

@luhmann `withSentryConfig` returns whatever you pass in as first argument. If you pass in an object, it will return an object. If you pass in a function, it will return...

@luhmann no worries! The changes around `withSentryConfig` we're indeed not the cleanest. That's on me. In the future, I recommend checking the type definitions signatures though because technically `withSentryConfig` can...

@Rizki36 Importing withConfig from a page is not a supported use-case. Why are you doing that?

@ianbayne What version of the Next.js SDK are you on?

@ianbayne can you try wiping your node_modules and reinstalling them? Thanks.

@ianbayne Can you try migrating your `_middleware.ts` from the legacy version ("_middleware") to the current version ("middleware.ts") - https://nextjs.org/docs/pages/building-your-application/routing/middleware#convention

@ianbayne Thanks for giving an update! We didn't consider that people may import the next config from components. I think this is something we should fix (by exporting the function...

@s-ashwin We recently added the [HttpClient integration](https://docs.sentry.io/platforms/javascript/configuration/integrations/plugin/#httpclient) that should collect that stuff and report it. It's currently not part of the default integrations so you have to add it manually.

Let's consider this resolved for now.

@ODVault do you have a release value configured?