更新 Jest 测试库后出现意外标记 (SyntaxError)

Unexpected token (SyntaxError) after updating Jest testing libraries

当 运行 我的测试套件使用 Jest 时,我遇到了要求我更新包的警告:

npm WARN deprecated jest-dom@2.1.1:  jest-dom has moved to @testing-library/jest-dom. Please uninstall jest-dom and install @testing-library/jest-dom instead, or use an older version of jest-dom. Learn more about this change here: https://github.com/testing-library/dom-testing-library/issues/260 Thanks! :)
npm WARN deprecated react-testing-library@5.9.0:   react-testing-library has moved to @testing-library/react. Please uninstall react-testing-library and install @testing-library/react instead, or use an older version of react-testing-library. Learn more about this change here: https://github.com/testing-library/dom-testing-library/issues/260 Thanks! :)

在package.json我改了下面

"jest-dom": "^2.1.1",
"react-testing-library": "^5.3.0"

"@testing-library/jest-dom": "^5.11.1",
"@testing-library/react": "^10.4.7"

当然还有来自

的导入语句
import "jest-dom/extend-expect";

import "@testing-library/jest-dom";

等等

在我删除旧的并添加新的之后,我遇到了多个错误,导致我的测试失败(仅在我的 Semaphore CI 设置中,而不是在我的本地机器上)。

FAIL src/redux/actions/tests/myActions.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/semaphore/my-app/client/node_modules/@testing-library/dom/dist/helpers.js:44
        } catch {// not using Jest's modern fake timers
                ^
    SyntaxError: Unexpected token {
      at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:403:17)
      at Object.<anonymous> (node_modules/@testing-library/dom/dist/pretty-dom.js:13:16)
      at Object.<anonymous> (node_modules/@testing-library/dom/dist/config.js:11:18)

我不是前端开发人员,所以我很高兴听到需要更多信息来提供帮助。非常感谢!

错误指的是 optional catch binding,它是现代 JS 特性,自 Node 10 起支持。这意味着 @testing-library/dom 包不支持旧的 Node 版本,这可以通过检查 engines 部分在其 package.json.

更好的解决方案是更新 Node.js,因为 8 已达到生命周期的尽头。或者,可以将软件包降级到较低的主要版本,或者按照错误提示将其列入白名单 transformIgnorePatterns 进行转译。

@Estus 的回答完全正确,我投了赞成票。如果您也在为您的 CI 使用 Semaphore,那么只是想添加实际修复,这样您就不需要像我一样花更多时间进行调查。

  • 确保您当前的节点版本至少是最新的稳定 LTS,并且您在本地使用的版本是您的测试通过的版本
  • 如果您还没有生成一个 .nvmrc 文件:node -v > .nvmrc
  • 确保在 semaphore.yml.
  • 每个 块中调用 nvm use

即使用外推的 for-your-project,版本如下:https://github.com/semaphoreci-demos/semaphore-demo-javascript/blob/master/.semaphore/semaphore.yml.

这将确保您的节点版本同步,并且应该解决您在 CI 中遇到的任何“SyntaxError: Unexpected token {”错误,前提是相同的测试在本地通过。如果不指定节点版本,Semaphore 默认使用 v8.17.0 (https://docs.semaphoreci.com/ci-cd-environment/ubuntu-18.04-image/#javascript-via-node-js)!因此,为什么任何未指定版本的人在升级任何 Jest 库时都会遇到此错误。