Failed to get mock metadata: node_modules/@sentry/react/cjs/index.js

[EvgenyOrekhov]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/react

SDK Version

7.16.0

Framework Version

React 18.2.0

Link to Sentry event

No response

Steps to Reproduce

1. Write a Jest test with the following contents:

import { init } from '@sentry/react';
jest.mock('@sentry/react');

Expected Result

No error

Actual Result

Test fails with Failed to get mock metadata: node_modules/@sentry/react/cjs/index.js

[EvgenyOrekhov]

The issue started happening after I upgraded @sentry/react from 7.15.0 to 7.16.0.

[EvgenyOrekhov]

Node.js version: 18.11.0
npm version: 8.19.2

[AbhiPrasad]

Thanks for writing in! I ran into this here when running yarn deduplicate - I wonder why 🤔. I had to fix this for some internal tests. Maybe the way we generated modules changed so we now require folks to use an explicit mocks file?

#5951

We did make some refactors around using global objects, perhaps that had some effect. #5948

Perhaps we have to change our entry points as was discussed in aws-amplify/amplify-js#4499?

@SimenB perhaps you have some context on what could be going on here?

[jackmccloy]

@AbhiPrasad I just wanted to report that I'm having the same issue. I haven't had a chance to dig into the links you shared and probably won't until the weekend, but this does seem to be an issue going from 7.15.0 to 7.16.0

[AbhiPrasad]

The temp fix here for everyone is to actually add mocks for your method, similar to what is done here: https://github.com/getsentry/sentry-javascript/pull/5951/files#diff-9b6a20828c3c1c7a7e897abb6d7c8a88130fc3ac55dad3cbd8d3ac92aff19fadR9

Probably also cleaner because you can control exactly what is being mocked, but that’s probably a matter of opinion on coding style.

[lobsterkatie]

@EvgenyOrekhov @jackmccloy - Two questions:

Does either of you have automock: true set in your jest config? That seemed to come up in a number of mentions of this error message in my googling.
Would one of you mind manually editing node_modules/@sentry/react/cjs/index.js to replace all instances of const with var and then trying to run the tests again?

[EvgenyOrekhov]

@lobsterkatie I don't have automock: true. Replacing all const with var in node_modules/@sentry/react/cjs/index.js didn't help, got the same error.

[kolorfilm]

I have the same issue. Suggestions don't work for me neither.

[scottmmjackson]

I'm getting the same issue but for mocking @sentry/browser. no automock: true in jest config.

EDIT: Confirmed that jest unit tests work in @sentry/react: 7.14.2 but are broken in the latest release.

EDIT2: Confirmed working in 7.15.0 - the release that broke this is 7.16.0

[johnhunter]

Can confirm the same issue with:

• @sentry/browser@7.16.0
• @sentry/node@7.16.0

I do not have automock: true in jest config.

This browser test fails:

import * as Sentry from '@sentry/browser';

jest.mock('@sentry/browser');

test('Sentry', () => {
  expect(Sentry).toBeDefined();
});

Failed to get mock metadata: <redacted>/node_modules/@sentry/browser/cjs/index.js

This node one fails:

const Sentry = require('@sentry/node');

jest.mock('@sentry/node');

test('Sentry', () => {
  expect(Sentry).toBeDefined();
});

Failed to get mock metadata: <redacted>/node_modules/@sentry/node/cjs/index.js

[AbhiPrasad]

This seems to be a jest bug - will be fixed by jestjs/jest#13513

[AbhiPrasad]

This will be fixed in the SDK with the next release - we recognize that not everyone can bump jest versions, but do want to shout out @Tofandel for fixing this in jest directly!

Appreciate the patience everyone!