Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jest: Unexpected token "function" #584

Open
DuncanBetts opened this issue Sep 24, 2019 · 0 comments
Open

Jest: Unexpected token "function" #584

DuncanBetts opened this issue Sep 24, 2019 · 0 comments

Comments

@DuncanBetts
Copy link
Contributor

DuncanBetts commented Sep 24, 2019

Comments welcome, but I intend on working on this myself.

Travis CI Failure:

FAIL  src/components/Home/Hero/ExchangeWidget/ExchangeWidget.test.js
  ● Test suite failed to run
    Jest encountered an unexpected token
    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.
    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".
    Here's what you can do:
     • 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/en/configuration.html
    Details:
    /home/travis/build/onitsoft/nexchange-open-client-react/node_modules/await-transaction-mined/index.js:8
        var transactionReceiptAsync = async function(txnHash, resolve, reject) {
                                            ^^^^^^^^
    SyntaxError: Unexpected token function
      at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:403:17)
      at Object.<anonymous> (node_modules/@colony/purser-metamask/staticMethods.js:20:30)
      at Object.<anonymous> (node_modules/@colony/purser-metamask/class.js:34:22)

This issue suggests amending the babelrc to use babel-preset-env "which keeps up to date with the latest language features" - currently the babelrc only includes react-app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant