-
Notifications
You must be signed in to change notification settings - Fork 41
Could not determine debug ID when using stdin with esbuild #688
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
Comments
Hey @TheHolyWaffle (nice username btw), thanks for reaching out! This is currently not supported and unfortunately I doubt this will be highly prioritised atm. Could you try to solve your use case with just Sentry CLI instead? |
I can workaround this by writing the content to a temporary file. And using that temporary file as the |
Environment
@sentry/esbuild-plugin
version3.2.1
esbuild
version0.25.0
Related to an earlier attempt to fix this by someone: #522
Steps to Reproduce
Expected Result
It should generate sourcemaps for the provided stdin content and upload them to Sentry. Replacing the
stdin
option with anentryPoints: ['path/to/file.js'],
does result in sourcemaps being generated and uploaded to Sentry.Actual Result
Logs:
No sourcemaps are uploaded
The text was updated successfully, but these errors were encountered: