You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run npm test on my pc , everything works well. But on Travis CI it failed, it seemed to be related to @vue/babel-preset-app, but I don't know how to fix it. And I can't find similar problems online.
> vue-cli-service test:unit
FAIL src/components/button/button.spec.js
● Test suite failed to run
Plugin 1 specified in "/home/travis/build/oGsLP/latios/node_modules/@vue/babel-preset-app/index.js" provided an invalid property of "default" (While processing preset: "/home/travis/build/oGsLP/latios/node_modules/@vue/babel-preset-app/index.js")
at Plugin.init (node_modules/jest-config/node_modules/babel-core/lib/transformation/plugin.js:131:13)
at Array.map (<anonymous>)
at Array.map (<anonymous>)
FAIL tests/unit/test.spec.js
● Test suite failed to run
Plugin 1 specified in "/home/travis/build/oGsLP/latios/node_modules/@vue/babel-preset-app/index.js" provided an invalid property of "default" (While processing preset: "/home/travis/build/oGsLP/latios/node_modules/@vue/babel-preset-app/index.js")
at Plugin.init (node_modules/jest-config/node_modules/babel-core/lib/transformation/plugin.js:131:13)
at Array.map (<anonymous>)
at Array.map (<anonymous>)
The text was updated successfully, but these errors were encountered:
Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).
I hope to see your helper-created issue very soon!
When I run
npm test
on my pc , everything works well. But on Travis CI it failed, it seemed to be related to @vue/babel-preset-app, but I don't know how to fix it. And I can't find similar problems online.The text was updated successfully, but these errors were encountered: