react-m | react-mobile | Frontend Framework library

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:

as webpack grows in size, they removed the polyfills in webpack5. Looks like you are using create-react-app (CRA) and webpack configuration is not exposed to the user in CRA. you can expose it using eject. you might have this script in package.json:

Node is currently treating your .js file as CommonJS. You need to tell Node to treat it as an ES module.

Try adding "type": "module" in your package.json file.

You can place it anywhere at the top level. E.g.:

You need to create a personal access token. You can find the instructions on creating personal access token in Creating a personal access token

Make sure you keep the access token secure & secret. After that you need to replace your current saved password in the device (laptop/desktop) with the access token. In macOS you can search for Keychain and find GitHub with an Internet password and replace it with your access token. For instructions, see Updating credentials from the macOS Keychain.

In Windows, it might be Credential Manager (I'm not sure). Check this out: How to update your Git credentials on Windows

react-markdown is shipped as js, add babel-jest as a transformer in your jest config

You were pretty close to achieving this. All you need is basically pass closeModal function down to EventDetail component like so:

and then call it inside navigateToRegistrationForm

By putting viewport and setViewport in the same context, you are forcing the sidebar to re-render each time the viewport changes, because it uses useContext(ViewportContext) — even though it only uses the setViewport part of the context. There are a few options:

• Reduce the performance impact of re-rendering by simply moving useContext(ViewportContext) into a sub-component, so that only the sub-component, not the whole sidebar, renders whenever the viewport is updated.
• If you only need one-way updates (sidebar button can set the map's viewport, but no other components need to know when the user moves around the map), then you could remove the setViewport call from the map.
• Put viewport and setViewport in separate contexts. This would mean two createContext() calls, but you would still keep a single ViewportProvider component that renders both providers, e.g. const [viewport, setViewport] = useState(); return .... Then, your sidebar can useContext only for the context it needs, and will not re-render when the other one changes.
• Use something like useContextSelector to replace const {setViewport} = useContext(ViewportContext) with const setViewport = useContextSelector(ViewportContext, (ctx) => ctx.setViewport).
• If you're considering broader architectural changes, libraries like React Redux or Recoil could provide alternative designs that would avoid this problem.

(By the way, in your code as written, I would recommend you wrap the value you pass to ViewportContext.Provider in a useMemo(() => ({viewport, setViewport}), [viewport, setViewport]), so that it doesn't trigger an update when the ViewportProvider is re-rendered if the viewport hasn't changed.)

For the 2nd question, you can set the code area height to full height when console view is hidden.

You can try this code: