cross-env | 🔀 Cross platform setting of environment scripts | Configuration Management library

I think the problem is that you are trying to use the deprecated babel-eslint parser, last updated a year ago, which looks like it doesn't support ES6 modules. Updating to the latest parser seems to work, at least for simple linting.

So, do this:

• In package.json, update the line "babel-eslint": "^10.0.2", to "@babel/eslint-parser": "^7.5.4",. This works with the code above but it may be better to use the latest version, which at the time of writing is 7.16.3.
• Run npm i from a terminal/command prompt in the folder
• In .eslintrc, update the parser line "parser": "babel-eslint", to "parser": "@babel/eslint-parser",
• In .eslintrc, add "requireConfigFile": false, to the parserOptions section (underneath "ecmaVersion": 8,) (I needed this or babel was looking for config files I don't have)
• Run the command to lint a file

Then, for me with just your two configuration files, the error goes away and I get appropriate linting errors.

For my version of this error, the issue seemed to be that I was importing a file with an alias in webpack from within the same directory.

To give an example, I had this directory setup:

To resolve this issue update the "passport" lib version in your package.json: from "passport": "^0.5.2", to "passport": "^0.4.0", so it's same as used in @nestjs/passport@8.0.1.

Update

It's likely a bug introduced in CRA5: issue

Using WDS_SOCKET_PORT=0 will allow the solution to work with all debug configurations.

=================================================

I notice that, after upgrading to CRA5, the react dev client starts to respect the current page's protocol. That is, if you are debugging your asp.net core project using https locally, the react dev client will also try to connect to node dev server with wss(websocket over TLS) which is not enabled by default. There are several ways to get around with this, the simplest way would be:

1. create a file with name .env.development in the same folder where lies your package.json.
2. put WDS_SOCKET_PORT= in .env.development you just created. should be 5001 by default if you are using the SPA template generated by dotnet cli.

This will allow the ws connection initiated by react dev client to be proxified to node dev server with UseReactDevelopmentServer middleware.

The issue is that you're running an old version of Laravel Mix. Another issue you will face is the @tailwindcss/form plugin will need to be updated as well.

Update the packages with:

I'm afraid you are running two instances of ESLint with different configs for each, let me explain why.

CRA already sets up ESLint (among other things) for you:

Under the hood, we use webpack, Babel, ESLint, and other amazing projects to power your app.

In CRA, ESLint is installed and run internally when you run start or build commands, so you see the output in the console while you develop the app, or build the final bundle. You can also get the lint output in your editor. CRA already includes a default config for ESLint, including several plugins.

You have installed ESLint individually in your project, and set it up within your own .eslintrc.json. That's absolutely fine! This is the usual way to lint your projects. The way you run this ESLint is by the lint command you added to your scripts.

So when you run start or build, you are linting your project with CRA's ESLint instance and config, but when you run lint you are linting your project with your ESLint instance and config. Their configs don't match 100%, hence the different errors reported.

You can check you have two instances of ESLint installed by running npm ls eslint, you'll see something like this:

There you can see a direct eslint dependency (the one you manually installed), and another eslint which belongs to react-scripts (the one installed as sub-dependency by CRA).

You have two options basically:

1. Remove your ESLint and customize CRA ESLint. You could uninstall your eslint dependency from your project, remove your custom .eslintrc.json, and extend CRA ESLint config. That has to be done through the eslintConfig key in your package.json. You wouldn't need to put there everything you had in your .eslintrc.json since most of it is already covered by CRA config. The downside of this option is that 1) you can't lint your code on demand with the npm run lint since CRA doesn't allow you to do so, and 2) you are tied to the ESLint plugins version used by CRA (e.g. they are using eslint-plugin-testing-library v3, but the latest is v5 and you can't use it).
2. Ignore ESLint from CRA (recommended). This is what I usually do. You can opt-out of the CRA built-in ESLint instance. To do this, you need to create a .env file in the root of your project, and then put DISABLE_ESLINT_PLUGIN=true inside. After that, CRA won't lint your code when running start or build, so it's up to you when to lint it with your lint command. Ideally, you'll run the lint command in your CI, and locally every time you commit files with lint-staged (this might not sound familiar to you, let me know if you need help to set up any of these), besides getting instant feedback of ESLint errors through your code editor (it should be really straightforward to set VSCode or WebStorm up to do so).

I hope this helps you, let me know if there is something else you want to discuss!

Your .next directory is empty when you create the container from that image.

update the docker file accordingly.

There was a new major release of node-fetch with breaking changes. If you downgrade node-fetch to a previous version, for example node-fetch@2.6.6, your code should work.

for more information: https://github.com/node-fetch/node-fetch/blob/HEAD/docs/v3-UPGRADE-GUIDE.md

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