React-scripts test command not working

Describe the bug

react-scripts test command stopped working after update to ^4.0.3 from ^3.0.0.

It shows this error on terminal:

● Validation Error:

  Watch plugin jest-watch-typeahead/filename cannot be found. Make sure the watchPlugins configuration option points to an existing node module.

  Configuration Documentation:
  https://jestjs.io/docs/configuration.html

error Command failed with exit code 1.

Nothing has changed on the code. Only react-scripts package. Tests were working fine before the update.
The project is not ejected and it is not intended to be.

Did you try recovering your dependencies?

Yes, I tried.
yarn version: 1.22.10

Which terms did you search for in User Guide?

I've search for 'react-scripts test' and 'watchPlugins' and all I found is that I need to eject the project. I don't understand why. It was never like that. So I think that is not the solution to the problem.

Steps to reproduce

Open a terminal on the CRA project root
Run yarn
Run yarn test

Expected behavior

I expect tests run fine. Like before updating to ^4.0.3.

Actual behavior

react-scripts test command stops working after update react-scripts library to ^4.0.3 from ^3.0.0.

It shows this error on terminal:

● Validation Error:

  Watch plugin jest-watch-typeahead/filename cannot be found. Make sure the watchPlugins configuration option points to an existing node module.

  Configuration Documentation:
  https://jestjs.io/docs/configuration.html

error Command failed with exit code 1.

Thank you :D

Same Problem here

Running into this as well.

facing the same issue.

I've fixed it by installing the plugin jest-watch-typeahead

I've fixed it by installing the plugin jest-watch-typeahead

Work for me!!! Thanks

Same here. Could be yarn issue?

I've fixed it by installing the plugin jest-watch-typeahead

Thank you!

Repro

I've also run into this same situation with a CRA currently, non-ejected, with react-scripts 4.0.3, though I reproduced it for 4.0.x in general. Same situation where I'm running the following inside my CRA:

yarn
yarn test

and then getting the same error:

Validation Error:

Watch plugin jest-watch-typeahead/filename cannot be found. Make sure the watchPlugins configuration option points to an existing node module.

Configuration Documentation:
https://jestjs.io/docs/configuration.html

Jest Config

Since this is through CRA, the only jest config options in my package.json are essentially:

"jest": {
    "testMatch": [
      "**/__tests__/**/*.test.[jt]s?(x)"
    ],
    "transformIgnorePatterns": [
      "<rootDir>/node_modules/(?!@private-repo-name)/"
    ]
  },

Running yarn test with additional options such as below causes the same validation error:
yarn react-scripts test --testPathPattern App.test.tsx

Application Structure

I suspect that this might be related to the structure of this application, as I've recently changed it.

Here's a simplified diagram of the (full-stack) project:

Root (express server)

📦 my-preexisting-project
|_ 📁 client // see below for structure ⬇️
|_ 📁 routes
|_ 📁 server
|_ 📁 test // currently empty 😞 😞 😞
|_ 📄  package.json
|_ 📄  babel.config.js, webpack.config.js, (...)

Client Application (made with latest CRA)

📦 client
|_ 📁 public
|_ 📁 src
|  |_ 📁 "__tests__"
|  |  |_ 📁 components
|  |  |_ 📁 setup // helpers surfaced by setupTests.tsx
|  |  |_ 📄 App.test.tsx
|  |_ 📁 assets
|  |_ 📁 components
|  |_ 📁 integrations
|  |_ 📁 pages
|  |_ 📁 utils
|_ 📄 package.json
|_ 📄 setupTests.tsx
|_ 📄 tsconfig.json, .env, (...)

Anyway, apologies in advance if I'm missing something simple (tooling/build stuff for full-stack apps is a bit new for me, and this project predates my work on it), but I mostly just wanted to document another case of this. If I find a work-around, fix, etc., I'll be sure to return and share for others.

I have had the same issue and one important thing to notice is that the newest released version of jest-watch-typeahead is now written in native ESM and will break with the following error:

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module

Make sure to install the version compatible with Jest 26 e non native ESM modules.

yarn add --exact jest-watch-typeahead@0.6.5

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

same problem here

Hello.
I created a related issue.
After adding the correct jest-watch-typeahead v.0.6.5 package as @giuliogallerini pointed out, the problems continues.
Thank you.

I noticed that I didn't have jest-watch-typeahead in my node_modules. Installing it solved the problem:

npm install --save-dev jest-watch-typeahead

That's a workaround of course rather than solving the problem.

changed travis yml

any update with this issue?

Encountered same issue

I didn't have the issue when moving to 4.0.3, but saw the issue when going to 5.0.0

Just found a linked issue that relates to my issue: #11792

Encountered same issue

The issue has to do with your node version. Update your node to the latest stable version to fix it.

I had the same error and I found a work around.

npm i -D --exact jest-watch-typeahead@0.6.5

then there'll be an error for the jest version, I changed it to version 27.0.0, same the ts-jest.

Had the same issue after updating react-scripts 4.0.3 → 5.0.1.

It's not necessary to add jest-watch-typeahead as a dependency to the package.json, no-save install was enough in my case:
npm install --no-save jest-watch-typeahead@1.1.0

Running npm ci might be more robust solution, though.

Navigation Menu

Repository navigation

React-scripts test command not working #11043

Describe the bug

Did you try recovering your dependencies?

Which terms did you search for in User Guide?

Steps to reproduce

Expected behavior

Actual behavior

Repro

Jest Config

Application Structure

Root (express server)

Client Application (made with latest CRA)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

React-scripts test command not working #11043

Description

Describe the bug

Did you try recovering your dependencies?

Which terms did you search for in User Guide?

Steps to reproduce

Expected behavior

Actual behavior

Activity

aschuermann-at-neusta commented on Jun 10, 2021

Elliot128 commented on Jun 23, 2021

kkgowtamasa commented on Jul 1, 2021

Warix3 commented on Jul 6, 2021

danpadua commented on Jul 29, 2021

MiroslavPetrik commented on Jul 30, 2021

k61b commented on Jul 30, 2021

seanmhanson commented on Oct 6, 2021

Repro

Jest Config

Application Structure

Root (express server)

Client Application (made with latest CRA)

ggwzrd commented on Oct 13, 2021

stale commented on Jan 9, 2022

MarcelDurganteDev commented on Feb 8, 2022

Huespal commented on Mar 10, 2022

dooman87 commented on Mar 13, 2022

wulinjie122 commented on May 10, 2022

jasonaravanis commented on May 31, 2022

shiraze commented on Jul 4, 2022

user2695 commented on Sep 3, 2022

gmmvllfrt commented on Sep 9, 2022

edloidas commented on Sep 13, 2022

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions