postcss-normalize | Use the parts of normalize.css | Style Language library

You need to force the ReactMarkdown to run on the client side

Finally, this problem has been solved.
Using yarn instead of using npm solved the problem.
Remove node_modules and yarn install
After that, the problem has gone away.
Thank you.

Since you are using create-react-app for this, there's no need to eject the webpack.config.js (since this is irreversible, I hope you have a git commit you can revert). So here's the general gist:

• You create a file called chatLoader.js outside of your react project (if you don't intend to learn how to configure this in the same webpack config, which might get a little tricky) and add babel transpilation and minification by yourself.
• This file contains something like (untested)

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).

UPDATE: After researching for a few hours, I've found a solution. If nothing works, install the package that gives you problems, for example, npm install postcss --save-dev.Then, add this to your package.json file:

A few developers are now slowly getting this hopefully temporary problem when they update their projects.

For example: https://github.com/facebook/create-react-app/issues/11012

Recommendation is to leave this on the todo list, and wait a few days while the package developers fix this (at least for the packages that already have been notified)

Then run audit fix again

In the meantime, one error in particular the 'high' severity one...

I had posed this question couple of weeks ago here.

You can overcome this by forcing a resolution of postcss to ^8.2.10 temporarily. I wouldn't anyway worry much as a patch is being done as we speak, so it's just going to be a matter of time before it gets resolved.

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.

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.