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
NOTE: This is not ready for merge. Opening PR to allow people a place to comment and discuss. NOTE 2: If you are a user of Jest, you do not need this PR in order to use Babel 7 and Jest together - that has worked since Jest 22 released in 2017. This PR is strictly upgrading internals and dropping support for Babel 6. If you have some changes which can help us land this, feel free to open up a PR a
I went through getting started but can't get jest to work. I use node v6.9.1, npm v3.10.8 and jest v17.0.3. I also tried --no-cache and --debug but nothing changes. I even moved test to __tests__ dir and renamed it accordingly. Do you want to request a feature or report a bug? bug What is the current behavior? no output, seems like no tests are being ran If the current behavior is a bug, please pr
Do you want to request a feature or report a bug? Report a bug. What is the current behavior? Calling console.log using the default testEnvironment of jsdom doesn't print to stdout. If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test. Clone h
🐛 Bug Report I started getting the dreaded SyntaxError: Unexpected token import error again for lodash-es. And I spent hours debugging it, because I already had .babelrc and package.json:jest configured properly ("modules": "commonjs", a jest.transform for babel-jest, and transformIgnorePatterns set to not ignore node_modules/lodash-es). After a lot of debugging and a little searching, it appears
Requires Babel "^7.0.0-0", but was loaded with "6.26.3". If you are sure you have a compatible version of @babel/core, it is likely that something in your build process is loading the wrong version. Inspect the stack trace of this error to look for the first entry that doesn't mention "@babel/core" or "babel-core" to see what is calling Babel. at throwVersionError (node_modules/@babel/plugin-propo
Versions: Yarn: v0.21.3 Node: v6.9.2 npm: 3.10.9 Ubuntu: 16.10 Installed using: yarn global add jest (With a chown at ~/.config/yarn/global/node_modules/) Command failed: jest -c lib/tools/testing/jest.config.json --no-cache --watch If I run jest -c lib/tools/testing/jest.config.json --no-cache testing works 100% fine. Error message: fs.js:1431 throw error; ^ Error: watch /home/fooBar/dev/blah/lib
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く