enzyme-to-json | Snapshot test your Enzyme wrappers | Testing library

I've recently joined a new organisation and they use a lot of CSS to hide/show elements.

First of all, is this good practice? I have always (in most cases) shown and hidden components using a boolean to add or remove it from the dom (this is also easy to test)

Whilst trying to add tests using @testing-library/react I've found that the classes are visible by using the identity-obj-proxy module.

However, when trying to test the functionality of an element being visible or not, it becomes difficult because I don't think the less code is being compiled.

Is it possible to compile less code so it will be reflected in the tests?

Could it be something to do with the classnames module being used?

failing test

FileUploadStatus.test.js

I am trying to use mini css extract plugin but it doesn't work. I couldn't find what should be the correct configuration. I am getting this: [webpack-cli] Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema. configuration.plugins[2] should be one of these: object { apply, … } | function Plugin of type object or instanceof Function. Details: configuration.plugins[2] should be an object: object { apply, … } Plugin instance. configuration.plugins[2] should be an instance of function. Function acting as plugin. error Command failed with exit code 2. Do I need to downgrade just webpack or webpack-cli also? Are there any other problem?

webpack.common.js:

Context: I'm using jest, typescript, babel, and material-ui in my project.

I've been investigating a performance issue with our unit tests that seem to be caused by most unit tests importing the entirety of material-ui because we're importing them from @material-ui/core. I've been trying to resolve this with a babel plugin, either using a custom plugin or the babel-plugin-transform-imports package which seems like it would do what I want as well.

The trouble is that the plugin never seems to be called. We're using ts-jest, so it goes through both the babel and typescript compilers. But it seems like typescript might be resolving all of the imports before babel can transform them.

I've considered just using babel to do all of the typescript compilation, but then have maintain the jest build process separately from the main build process that we use. And I'm currently having issues getting it to run properly anyway. I'm also considering doing a custom jest transformer, but that seems like it would be more fragile and harder to maintain than a babel plugin.

Jest configuration:

package.json

I have recently ejected Create-React-App and reconfigured many stuff! however, I still can't get the tests working... I get the following error :

when i try to build my project with yarn run build i get errors that are not exist in my code my code is clean it works fine in my local. I've been stuck for two weeks to resolve this problem please help me to solve this problem. this the errors that i get

node version: v10.15.3

webpack: 4.30.0 this is my package.json

I Know that there is a lot of topic about this, but since none of them work, I must make a new one, I'm quite confused as why my electron app doesn't launch when I used yarn dev for my project, but when my friends try it, in his laptop, he can run and the apps launch normally without any problem, so Is there anyone here ever face the same problem with me? if there is someone, how can you solve this problem?

this is what my terminal looks like:

for information I used:

Just got this message from Apple this morning: