Deprecation messages are stored in the devtools-frontend repo at front_end/models/issues_manager/DeprecationIssue.ts.

[ezur1]

getting this error -
Deprecation messages are stored in the devtools-frontend repo at front_end/models/issues_manager/DeprecationIssue.ts.
not sure how to reach the deprecation messages.

please help

[rchl]

Seems like this is Chrome message and not related to this module at all.

[AnthonyRuelle]

Hi,

I've had the same problem with my project for a few weeks and it's getting annoying.
Why does Sentry raise this error? What does that mean ?

Could it be related to a too old version that could be solved by this PR?
#425

[AnthonyRuelle]

Up,

it's really very annoying, we are constantly polluted

[rchl]

As I wrote, this seems like a message triggered by chrome. At least it seems so after short googling.

Maybe it's sentry that indirectly triggers those but I can't tell since I'm not seeing those myself.

[GregorSondermeier]

Hello,

we got a Spike Warning from sentry because this error pollutes our issue log. Our website uses Nuxt 2. Is there any advice on how to avoid this message being logged?

[rchl]

Check sentry documentation for how to ignore specific errors

[GregorSondermeier]

Our solution:

In our nuxt.config.js we have set the following:

  ...
  sentry: {
    ...
    clientIntegrations: {
      ReportingObserver: false,
    },
  },
  ...

Documentation:
https://sentry.nuxtjs.org/sentry/options#clientintegrations

We are aware that this doesn't fix the root issue, but at least it prevents these warnings from polluting our Sentry log :)

[rchl]

I'm disabling those noisy reports in the latest version: #560