When using Jest to test a component that renders DynamicContextProvider, you might run into an error like:

FAIL  app/page.spec.tsx
  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    For information about custom transformations, see:


    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import { allocUnsafe } from './alloc.js';

    SyntaxError: Cannot use import statement outside a module

      10 |       some text
      11 |     </DynamicContextProvider>
    > 12 |   );
         |               ^
      13 | }
      14 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1496:14)
      at Object.<anonymous> (app/page.tsx:12:19)
      at Object.<anonymous> (app/page.spec.tsx:7:54)

This can be easily fixed by mocking DynamicContextProvider:

jest.mock("@dynamic-labs/sdk-react-core", () => ({
  DynamicContextProvider: ({ children }) => children,