Jest encountered an unexpected token after update

After updating from v 1.1.1 to most recent 2.1.4 I got this error:

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:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

Details:

    /Users/pawel/moje/serverless-hexagonal-template/node_modules/filter-obj/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export default function filterObject(object, predicate) {
                                                                                      ^^^^^^

    SyntaxError: Unexpected token 'export'

      at Runtime.createScriptFromCode (../node_modules/jest-runtime/build/index.js:1796:14)
      at Object.<anonymous> (../node_modules/aws-testing-library/src/common/dynamoDb.ts:1:1)

I’ve tried many different solutions fount on the internet but nothing seems to work.

My jest version is 28.1.1 and node is 14.

[erezrokah]

Hi all and thanks for the workaround @RaphaelManke. I think my suggestion in https://github.com/erezrokah/aws-testing-library/issues/635#issuecomment-1167686784 does something similar via a preset: https://github.com/erezrokah/aws-testing-library-examples/blob/8cbffeb58725baa168a1d10fa8568369146cf3dc/jest.config.js#L6 https://github.com/erezrokah/aws-testing-library-examples/blob/8cbffeb58725baa168a1d10fa8568369146cf3dc/jest.config.js#L6

This is a jest issue, see related issues in https://github.com/facebook/jest/issues?q=is%3Aissue+Jest+encountered+an+unexpected+token and specifically https://github.com/facebook/jest/issues/9430.

However I’ll try to see if there’s anything to be done on aws-testing-library side. It will probably take me a week or so to look into this

[RaphaelManke]

Hi we fixed it by doing the following

1. add Babel jest to the project https://jestjs.io/docs/getting-started#using-babel
2. add to your jest config

transformIgnorePatterns: [
   `node_modules/(?!aws-testing-library|filter-obj)`,
],
transform: {
    "^.+\\.jsx?$": "babel-jest",
    "^.+\\.tsx?$": "ts-jest",
},