我目前正在GitHub页面上设置Docusaurus v2网站。我已经为自己的组件编写了自己的Jest和酶测试。当前Jest被列为devDependency
,而我的.travis.yml
如下:
# .travis.yml
language: node_js
node_js:
- '10'
branches:
only:
- master
cache:
npm: true
install:
npm i
script:
- git config --global user.name "${GH_NAME}"
- git config --global user.email "${GH_EMAIL}"
- echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
- npm t && GIT_USER="${GH_NAME}" npm run deploy
我更新了package.json
笔录部分,以相对于node_modules
的方式来开玩笑,如下所示:
"test": "cross-env NODE_ENV=test ./node_modules/jest/bin/jest.js --detectOpenHandles"
这在travis中运行得非常好,我看到我所有的测试都通过了。我遇到的问题是它试图将站点部署到GitHub页面时,如scripts
:.travis.yml
中npm t && GIT_USER="${GH_NAME}" npm run deploy
部分的最后一行所示。随后,我收到以下错误:
ReferenceError: jest is not defined
(undefined) ReferenceError: jest is not defined
at Module.module.exports.Object.defineProperty.value (main:26124:1)
at __webpack_require__ (main:21:30)
at Promise.resolve.then (main:79206:682)
Error: Failed to compile with errors.
at compiler.run (/home/travis/build/myorg/myrepository/node_modules/@docusaurus/core/lib/commands/build.js:37:24)
at finalCallback (/home/travis/build/myorg/myrepository/node_modules/webpack/lib/MultiCompiler.js:254:12)
at runWithDependencies.err (/home/travis/build/myorg/myrepository/node_modules/webpack/lib/MultiCompiler.js:277:6)
at done (/home/travis/build/myorg/myrepository/node_modules/neo-async/async.js:2931:13)
at runCompilers (/home/travis/build/myorg/myrepository/node_modules/webpack/lib/MultiCompiler.js:181:48)
at err (/home/travis/build/myorg/myrepository/node_modules/webpack/lib/MultiCompiler.js:188:7)
at compiler.run (/home/travis/build/myorg/myrepository/node_modules/webpack/lib/MultiCompiler.js:270:7)
at finalCallback (/home/travis/build/myorg/myrepository/node_modules/webpack/lib/Compiler.js:257:39)
at hooks.done.callAsync.err (/home/travis/build/myorg/myrepository/node_modules/webpack/lib/Compiler.js:273:13)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/travis/build/myorg/myrepository/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:42:1)
at AsyncSeriesHook.lazyCompileHook (/home/travis/build/myorg/myrepository/node_modules/tapable/lib/Hook.js:154:20)
at onCompiled (/home/travis/build/myorg/myrepository/node_modules/webpack/lib/Compiler.js:271:21)
at hooks.afterCompile.callAsync.err (/home/travis/build/myorg/myrepository/node_modules/webpack/lib/Compiler.js:681:15)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/travis/build/myorg/myrepository/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
at AsyncSeriesHook.lazyCompileHook (/home/travis/build/myorg/myrepository/node_modules/tapable/lib/Hook.js:154:20)
at compilation.seal.err (/home/travis/build/myorg/myrepository/node_modules/webpack/lib/Compiler.js:678:31)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] deploy: `docusaurus deploy`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] deploy script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
我可能是错的,但是我相信这是因为我的测试已作为代码库的一部分进行部署,而就算是devDependency
,它目前还不存在;因此,当在我的*.spec.js
文件(即jest.mock(...)
)中使用webpack时,找不到它。因此,我认为添加笑话作为正常依赖项可以解决此问题,尽管您可以理解,这既不理想也不正确。作为参考,我的测试文件不在__TESTS__
或任何形式的测试目录中。在遵循容器模式时,我所有的规范文件都与它们正在测试的文件相邻。其结构与此类似:
components
- Header
- HeaderComponent.js
- HeaderComponent.spec.js
- HeaderContainer.js
- HeaderContainer.spec.js
- Header.module.css
快速注解:] >> [在这种情况下,我觉得将它们分成一个容器更干净。除了使开玩笑成为常规依赖之外,还有其他更好的方法来解决此问题吗?我需要的设置是:
我目前正在GitHub页面上设置Docusaurus v2网站。我已经为自己的组件编写了自己的Jest和酶测试。目前Jest被列为devDependency,而我的.travis.yml ...