react-dev-utils | Our fork of react-dev-utils | Frontend Framework library

I am trying to set up my first Gatsby website. After running npm install -g gatsby-cli, I do gatsby new gatsby-starter-hello-world https://github.com/gatsbyjs/gatsby-starter-hello-world (just like the website https://www.gatsbyjs.com/starters/gatsbyjs/gatsby-starter-hello-world/ says) to download the hello world starter. When I run gatsby develop I see the following error

I am learning react, specifically with reactjs/toolkit for this section, and am going through a few basic examples to help teach myself where I am faking someone logging into their account. I understand the issue of my error but I cannot figure out how to solve it. As far as I can see my code is completely correct because my previous examples have followed the exact same pattern. The issue comes from my authSlice when it is imported. In the source file, it has access to authSlice.actions.login etc, but once imported it does not. For whatever reason it does not register login(){} or logout(){}. So when I attached the form to my submission handler this error is thrown. I think this is the issue because when I console log the actions I do not see my login or logout actions. I could also be wrong on this too, but I will attach the actual error at the end

I have my store in a separate file as follows:

When installing dependencies for a create-react app(version 5.0.0) using pnpm dlx and pnpm import, i get a warning that peer dependencies should be installed. The dev environment for react spins up just fine. This warn message does not show up when using npx. How can i fix this warn message other than installing the peer dependencies?. Thanks in advance.

What i did:

1. Create react app using pnpm dlx in the command-line

I have a monorepo that uses lerna, in that monorepo i have one api and two frontends, in both projects i have the same exact error when starting the projects

project: multi C:/Users/userName/programing/work/myProject/node_modules/@pmmmwh/react-refresh-webpack-plugin/client/ReactRefreshEntry.js C:/Users/userName/programing/work/myProject/node_modules/react-dev-utils/webpackHotDevClient.js ./src/index.jsx project: Cannot find file: 'ReactRefreshEntry.js' does not match the corresponding name on disk: 'C:\Users\UserName\programing\work\myProject\node_modules@pmmmwh\react-refresh-webpack-plugin\client\work'.

I already tried

• uninstalling/updating/deactivating react devtools extension
• deleting the hole project and installing all again
• recovering dependencies

as additional information
OS: Windows 10 10.0.19042
CPU: (4) x64 Intel(R) Core(TM) i3-7020U CPU @ 2.30GHz
Node: 14.15.1
Yarn: 1.22.5
Edge: Spartan (44.19041.1266.0), Chromium (96.0.1054.62)
react: 17.0.2 react-dom: 17.0.2
react-scripts: 4.0.3

I have upgaded m project Node version with all dependancies now I am attempting upgrade to Webpack 4 to Webpack 5. However when I run npm start I get this error. Strange thing is I don't use applyWebpackOptionsDefaults anywhere and after scouring the node_modules I see that it is used in the webpack lib quite a few times. Can anyone tell me what I am doing wrong? Is there a package I haven't updated? What am I missing?

Invalid options object. Dev Server has been initialized using an options object that does not match the API schema.

• options has an unknown property 'before'. These properties are valid: object { allowedHosts?, bonjour?, client?, compress?, devMiddleware?, headers?, historyApiFallback?, host?, hot?, http2?, https?, ipc?, liveReload?, magicHtml?, onAfterSetupMiddleware?, onBeforeSetupMiddleware?, onListening?, open?, port?, proxy?, server?, setupExitSignals?, static?, watchFiles?, webSocketServer? }

Here is the package.json:

How can I deploy a react app without having to change html scripts on my customers websites every time.

Some of my customers need a chat interface on their websites to allow website visitors to chat with a chatbot. This chatinterface is build using:

While running npx create-react-app my-app, I am getting 10 moderate severity vulnerabilities. Not able to fix even after running npm audit fix or npm audit fix --force. When I run npm audit fix --force i get more 44 vulnerabilities (25 low, 5 moderate, 14 high), then again if I run same command to fix I get 10 moderate severity vulnerabilities. This keeps on going in cycles each time I run command.

when updating webpack from 4 to 5, I got the error: