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
console integration fails - node: ERROR Cannot read property 'options' of null #1945
Comments
Update: I have to disable it by using following config though:
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).
According to the error trace it must be related with this line of code: |
+1 |
1 similar comment
+1 |
is this issue still present even with our new versions of SDKs? |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Haven't seen it for a while, i guess it's okay to close this. In case it pops up again, i will open a new one |
Package + Version
@sentry/browser
@sentry/node
raven-js
raven-node
(raven for node)Version:
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/node@4.5.0 solves the issue.
I'm out of ideas, can anyone shed light on this issue?
Thanks,
Simon
The text was updated successfully, but these errors were encountered: