Andrei comments

Results 190 comments of


                                            Andrei

[Sentry] Express is not instrumented. This is likely because you required/imported express before calling `Sentry.init()`

Hi there, Things changed in v8 a bit, most integrations are now automatically added and you no longer have to take care of those (with the exception of `nodeProfilingIntegration` in...

[Sentry] Express is not instrumented. This is likely because you required/imported express before calling `Sentry.init()`

Have you updated to `8.2.1` yet? Same result? Could you please provide - node version you are running - the updated code snippets after your migration attempts (`instrument.ts` and `main.ts`)...

Webpack plugin uploads source maps on development mode

As a workaround, setting `sourcemaps.disable` to `true` should now work (see https://github.com/getsentry/sentry-javascript-bundler-plugins/pull/587). Backlogging the dev mode improvement.

ng build stuck after successful build since sentryWebpack v2

Yes, so the workaround is either to downgrade or to use sentry-cli. We are thinking of refactoring unplugin out but have not yet committed to it.

[Sentry] Express is not instrumented. This is likely because you required/imported express before calling `Sentry.init()`

could you please post snippets of `instrument.ts` and the top of your app where you import sentry and express and setup the handler?

[Sentry] Express is not instrumented. This is likely because you required/imported express before calling `Sentry.init()`

Hey @Nabil372, thank you for providing a sample project. I've had a quick look over it, you do have performance (tracing) enabled so that's not the issue. I see that...

[Sentry] Express is not instrumented. This is likely because you required/imported express before calling `Sentry.init()`

@amiranvarov could you please update to the latest SDK? Should be `8.3.0` at the time of writing and report back? We updated some of the warnings around this.

[Sentry] Express is not instrumented. This is likely because you required/imported express before calling `Sentry.init()`

@cyrus-za just to make sure, `SENTRY_TRACE_SAMPLE_RATE` is set? Could you try hard coding it to `1.0`?

Re-Export RouterContext for more control

Having access to the router context would make it easier for third party libraries to interact with the router as well. In Sentry's case, [we export a HOC to wrap...

feat(node): Add `@sentry/node/preload` hook

> How does this differ from using `--import @sentry/node/import`? I can see the code differenced but why are these differences required? > > I assumed `--import @sentry/node/import` would load `import-in-the-middle`...