Charly Gomez

Closing this due to inactivity - we should discuss these specific use cases in https://github.com/getsentry/sentry-javascript and then add documentation if needed.

Hey @MWhite-22 thanks for reaching out. > If there is a myriad of other "enhancements" on by default then I would like to A: know about them, and B: disable...

@vasilev-alex did you try bumping the memory limit with `max_old_space_size=8192` in your build command? And just for completeness: uploading sourcemaps via CLI is documented [here](https://sentry-docs-git-docs-centralize-nextjs-initial-flow.sentry.dev/platforms/javascript/guides/react/sourcemaps/uploading/cli/)

Good you have a working solution for now! We're currently testing some improvements in debugId upload so this might affect this one as well.

@obecny how would you detect that in dev mode? The domains would probably differ from prod, e.g. everything could run on the same domain locally I think.

Oh so you would want to warn every user running locally – what I referred to was how to detect a potential cors issue in prod when users are running...

@OllieJennings we're currently busy working on a bigger change in the Next.js SDK, I will re-visit this afterwards (there are still tests failing atm) – I know this is a...

@lforst lol this approach worked locally with yarn pnp

Hey @max-prtsr , is there a reason why you manually add these headers to your request on the python side? They should be attached automatically anyway if you're using the...

@max-prtsr For python: [Documentation about injecting tracing information to http requests](https://docs.sentry.io/platforms/python/tracing/trace-propagation/custom-instrumentation/#inject-tracing-information-into-http-requests). [Documentation about limiting propagation targets](https://docs.sentry.io/platforms/python/tracing/trace-propagation/limiting-trace-propagation/).