jest test useAnalysis.test.tsx is failing

[bobular]

Looks like tests haven't been run in a while.

yarn add --dev babel-jest is needed to get yarn test to work.

Two of the three existing tests work fine but useAnalysis is failing (error message below) and after trying to fix it I have given up. (This seems the most relevant stackoverflow but I couldn't get any of the suggestions to work. In particular trying to transform our @VEuPathDB modules... When it works it's great, but when it doesn't the node ecosystem is so opaque...)

    Details:

    /home/maccallr/Desktop/EDA/web-eda/node_modules/@veupathdb/wdk-client/lib/Utils/Task.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import { noop } from 'lodash';
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      3 | import { differenceWith } from 'lodash';
      4 |
    > 5 | import { Task } from '@veupathdb/wdk-client/lib/Utils/Task';
        | ^
      6 |
      7 | import {
      8 |   AnalysisClient,

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
      at Object.<anonymous> (src/lib/core/hooks/analysis.ts:5:1)

Jest did try to offer some guidance:

    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