@sentry/profiling-node: ReferenceError: __DEBUG_BUILD__ is not defined #10525
Assignees
Comments
|
I got this on my e2e test - something is up https://github.com/getsentry/sentry-javascript/actions/runs/7804351046/job/21287026518?pr=10527 |
|
I'm also experiencing this in a project that just updated to |
|
Opened #10534 to fix, sorry for the trouble everyone! |
AbhiPrasad
added a commit
that referenced
this issue
Feb 6, 2024
Fixes #10525 When writing the rollup config, we didn't include the debug build plugin. This led to things not be replaced properly as `profiling-node` bundles everything into a single file. This was also causing issues in our CI: https://github.com/getsentry/sentry-javascript/actions/runs/7804351046/job/21287026518?pr=10527 Backporting this fix to v7 so we can do a `7.100.1` release after we merge this in.
|
We are going to merge in one more fix (#10536), and then we'll cut a patch release with this fix. Thanks for your patience everyone, sorry again for the inconvenience. |
mydea
pushed a commit
that referenced
this issue
Feb 7, 2024
Fixes #10525 When writing the rollup config, we didn't include the debug build plugin. This led to things not be replaced properly as `profiling-node` bundles everything into a single file. This was also causing issues in our CI: https://github.com/getsentry/sentry-javascript/actions/runs/7804351046/job/21287026518?pr=10527 Backporting this fix to v7 so we can do a `7.100.1` release after we merge this in.
This was referenced Mar 27, 2024
This was referenced Apr 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/node
SDK Version
7.100
Framework Version
No response
Link to Sentry event
No response
SDK Setup
No response
Steps to Reproduce
I can not deploy because a reference to
__DEBUG_BUILD__variable is not defined.Expected Result
I expect the reference to removed at build time.
Actual Result
Starting package crashes.
The text was updated successfully, but these errors were encountered: