jest-watch-typeahead | Jest watch plugin for filtering test | Unit Testing library

This is what the Jest documentation says about how it finds test files:

By default it looks for .js, .jsx, .ts and .tsx files inside of __tests__ folders, as well as any files with a suffix of .test or .spec (e.g. Component.test.js or Component.spec.js). It will also find files called test.js or spec.js.

Since the setupTests.js filename does not meet this criteria, Jest does not recognize it as a test file. If you rename the file to end with .test.js or move it into a __tests__ folder, Jest should be able to find it and run the test. If you need to keep the filename as is, this default behavior can be changed by setting testRegex in jest.config.js (read more about this setting here).

The setupFiles property in jest.config.js is used for setting up the environment before the tests actually run. The documentation for that setting can be found here, but it doesn't appear to be necessary to do any setup for this case based code you provided.

Cause: babel-jest uses babel configuration that is loaded based on the location of the file that is going to be transformed. After ejecting create-react-app your package.json probably contains:

Managed to fix this by adding these lines to the package.json file if anyone is having a similar problem.

You're in a loop because react-scripts@1 has some vulnerable dependencies and react-scripts@4 has different vulnerable dependencies, so you're bouncing back and forth between them. The first time you run npm audit --fix, you update to react-scripts@4.x, and when you run it again, it downgrades you to react-scripts@1.x to remove the vulnerable dependencies in the 4.x version.

As of this writing, if you run npx create-react-app my-app, you get react-scripts@4 (and the warning about 22 vulnerabilities) so maybe run npm audit --fix to get to that state, run your tests to make sure nothing broke, and go to https://www.npmjs.com/package/react-scripts from time to time to check for a release that bumps the dependencies (and/eor run npm audit from time to time without the --fix to see if it updates it automatically).

Check out this answer React Native Jest SyntaxError: Duplicate __self prop found

Also refer: https://reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html

Update @babel/core and @babel/plugin-transform-react-jsx

No. What Webpack ends up including is not something published or reported. Using react-scripts alone would seen hundreds of modules and versions being shipped in production. Any library you add on top just adds to that weight.

With tree shaking and build deps, you can't rely upon that requires at all. Some of those, like Jest or ESLint, are dev-only. They have no runtime. Others will. Some runtime deps will be shaken out too, so can't rely on just recognizing the lib.

I just solved it. I have seen many people saying to reinstall the node_modules, that, unfortunately, did not work for me, here is listed what I have tried to do:

1. Deleting the package-lock.json
2. Deleting node_modules
3. Removing jest from the dependencies and devDependencies
4. Running npm install (to install the node_modules again)

None of that worked for me. What I did was, I removed jest from my computer, the whole app. Go to your cmd and type "npm rm jest", which should seal the deal. After that, I ran "npm install" inside my project on VSCode "ctrl + j" to open the terminal, then just went with "npm start" and it is now working. I am guessing that will also work if you get the same problem with other dependencies like Babel or something (I'm just guessing though, I am no expert in react or node).

Best of luck to anyone who is facing the same problem

ESLint reports config errors as an issue with the first line of files it's applied to. As @sleepwalker mentioned it should have to do with your eslint config (e.g. .eslingrc).

Looking up the first rule that is failing: no-empty-label.

It has the following warning:

This rule was removed in ESLint v2.0 and replaced by the no-labels rule.

So it's likely you need to follow the error recommendations, and make those modifications to your ESLint config.

Example:

These things usually happens when I'm using VSCODE. Usually there are 3 things I do to Fix. If this config works for you in other projects it might be usefull.

1. Run the "Reload Window" in VSCODE, usually fix the problem for me
2. Delete the node_modules and reinstall de deps, I use yarn and it fixed the problem before
3. It might worth reacreate manually the .eslintrc . Maybe there's an update in CRA and things changed. Usually I start a new project and run eslint --init and start creating a new eslintrc

And it's cool to check if the eslint plugin is workin in your IDE.

obs : I woul'd post this as a comment, however I can't yet.