browserslist | 🦔 Share target browsers between different front

I got two different solution.

1. remove

https://github.com/typescript-eslint/typescript-eslint/issues/3982

It seems to be a compatibility problem

Here is a workaround. Delete "proxy": "http://localhost:6000". Install package http-proxy-middleware with command npm install http-proxy-middleware --save. Create a file setupProxy.js inside your src folder. Add these lines inside:

First, this error message is indeed expected on Jan. 11th, 2022.
See "Improving Git protocol security on GitHub".

January 11, 2022 Final brownout.

This is the full brownout period where we’ll temporarily stop accepting the deprecated key and signature types, ciphers, and MACs, and the unencrypted Git protocol.
This will help clients discover any lingering use of older keys or old URLs.

Second, check your package.json dependencies for any git:// URL, as in this example, fixed in this PR.

As noted by Jörg W Mittag:

There was a 4-month warning.
The entire Internet has been moving away from unauthenticated, unencrypted protocols for a decade, it's not like this is a huge surprise.

Personally, I consider it less an "issue" and more "detecting unmaintained dependencies".

Plus, this is still only the brownout period, so the protocol will only be disabled for a short period of time, allowing developers to discover the problem.

The permanent shutdown is not until March 15th.

As in actions/checkout issue 14, you can add as a first step:

Chart.js is treeshakable since chart.js V3 so you will need to import and register all elements you are using.

There is an update to mini-css-extract-plugin in version 2.5.0. I temporarily fixed it by adding in package.json:

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.

react-router v6 doesn't use RouteComponentProps anymore. Here are some links with examples on how to change route and how to use params on v6 with some links where you can find more informations:

For changing route (old history.push)

If you want to change the route after the login is successful react-router docs specify

In v6, this app should be rewritten to use the navigate API. Most of the time this means changing useHistory to useNavigate and changing the history.push or history.replace callsite.

So basically instead of having somthing like

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!