Tim Fish

This is usually an incompatibility between the native module and the node version you're compiling against. `node-ffi` has not been updated to work in Node v10 that Electron v3 uses....

I recently added some integration tests for `@sentry/node-experimental` that test `mysql2`. The node experimental package uses OpenTelemetry for its auto-instrumeted span creation. When v8 of the JavaScript packages ships, otel...

> +1 -- this is a missing piece for us with Sentry! Have you tried the latest beta release? `mysql2` is supported in v8.

Terser itself doesn't appear to have minify levels, all the different options are configured individually: https://github.com/terser/terser?tab=readme-ov-file#compress-options What level option is being referred to in the webpack config? https://webpack.js.org/plugins/terser-webpack-plugin/

Ah ok so it's the inline levels! `options: { compress: { inline: 1 } }`

I've added tests for both webpack 4 and 5 and backported them to the v7 branch to see if there are any failures. We don't see any issues with the...

Maybe my test cases should at least access more of the SDK API?

No, not sure what's causing this. In the next major, `dynamicRequire` is no longer used.

Yep, no problem. Would this flag still be stored under the same `globalThis._sentryModuleMetadata` or use an extra global store? Any preferences over the integration name and corresponding bundler plugin option?

Great, one of the plus points of it being pure JavaScript! One downside is that command names are limited to valid JavaScript. Automatic camel to kebab conversion `buildTs` -> `build-ts`...