react-test | Another React JS example

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:

craco's Github readme, states that it is supporting Create React App (CRA) 4.*. By this statement, I'm assuming CRA 5 is not officially supported by craco.

However, this repository utilizes both CRA 5 and craco (but I have not verified that it is working). Use this repository to compare your setup (after verifying that the linked repositry is working), and try different settings/configs to see if you get further.

can you give your

• package.json
• node version

I think that's because of the babel issue / your node version, because it cannot transpile the optional chaining https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining

maybe tried using latest LTS node version? because as far as I know, the latest LTS node version already support optional chaining

I would like to suggest you to use testing-library/react which could be use smoothly with jest and provide async methods

Your test would become something like:

The difference between .toBeInTheDocument() and .toBeVisible() are explained clearly in the doc.

In short: An element can be present in the document but not visible to the user.

E.g.

Okay so it seems like Remote Debugging is not possible after installation of reanimated 2, using Flipper for debugging instead

Turns out that the cause for this was that the exported component got mocked, due to that I had automock set to true in my jest config.

Changing this in jest.config.js:

Update on this one, I finally found why i couldn't import my component without require, it was due to "moduleResolution": "node". Removing the line fixed the issue

Figured out my own issue. I had set global.window = {} in the jest.setup.js file earlier. @testing-library/react-native uses a timers.js file in which they refer to globalObj which they obtain from the following: const globalObj = typeof window === 'undefined' ? global : window;. As window was not technically undefined, globalObj was being set to {} and did not have access to global functionality.