Sentry-javascript: console integration fails - node: ERROR Cannot read property 'options' of null

Created on 14 Mar 2019 · 3Comments · Source: getsentry/sentry-javascript

[x] Review the documentation: https://docs.sentry.io/
[x] Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
[x] Use the latest release: https://github.com/getsentry/sentry-javascript/releases

Package + Version

[ ] @sentry/browser
[x] @sentry/node
[ ] raven-js
[ ] raven-node _(raven for node)_
[ ] other:

Version:

4.6.4

Description

I get the following error, unfortunately I'm still not able to track it down. This error is "new", but I'm not sure where it comes from. It worked before already.
ERROR Cannot read property 'options' of null

at node_modules/esm/esm.js:1:193386
at ss (node_modules/esm/esm.js:1:193417)
at node_modules/esm/esm.js:1:195337
at node_modules/esm/esm.js:1:195465
at node_modules/esm/esm.js:1:194201
at Object.apply (node_modules/esm/esm.js:1:193991)
at Console.log (node_modules/@sentry/node/src/integrations/console.ts:86:36)
at t.state.user.login.sessionIdCookie.t.state.user.login.loggedIn.t.dispatch.catch.t (webpack/bootstrap:2:0)

I've tried disabling intergrations one by one, or all at once: no change. Not even downgrading to @sentry/[email protected] solves the issue.

I'm out of ideas, can anyone shed light on this issue?

Thanks,
Simon

Source

simllll

Most helpful comment

Update:
disabling all modules does actually "resolve" the issue.
With version 4.5.0 and also with version 4.6.4.

I have to disable it by using following config though:

defaultIntegrations: false,
integrations: [],

I tracked it down to the console intergration, something isn't working out in my setup suddenly. It seems it's "only" happening when axios is failing with a request. (no idea how this can be related).

integrations: [
            new Integrations.Dedupe,
            new Integrations.ExtraErrorData,
            new Integrations.InboundFilters,
            new Integrations.FunctionToString,
            // new Integrations.Console, <--- starts working again
            new Integrations.Http,
            new Integrations.OnUncaughtException,
            new Integrations.OnUnhandledRejection,
        ]

According to the error trace it must be related with this line of code:
"message: util.format.apply(undefined, arguments),"
even though I cannot see any "options" (ERROR Cannot read property 'options' of null) there, can it be that "arguments" is somehow processed wrongly here?

simllll on 14 Mar 2019

👀2 👍2

All 3 comments

Update:
disabling all modules does actually "resolve" the issue.
With version 4.5.0 and also with version 4.6.4.

I have to disable it by using following config though:

defaultIntegrations: false,
integrations: [],

integrations: [
            new Integrations.Dedupe,
            new Integrations.ExtraErrorData,
            new Integrations.InboundFilters,
            new Integrations.FunctionToString,
            // new Integrations.Console, <--- starts working again
            new Integrations.Http,
            new Integrations.OnUncaughtException,
            new Integrations.OnUnhandledRejection,
        ]

simllll on 14 Mar 2019

👀2 👍2