Unit Test for findNodeHandle Error Behavior

[yungsters]

Summary

As promised on #29627, this creates a unit test for the findNodeHandle error that prevents developers from calling it within render methods.

How did you test this change?

$ yarn test ReactFabric-test.internal.js

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-compiler-playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 12, 2024 11:34pm

[react-sizebot]

Comparing: 23830ea...9fa4946

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name	+/-	Base	Current	+/- gzip	Base gzip	Current gzip
oss-stable/react-dom/cjs/react-dom.production.js	=	6.68 kB	6.68 kB	+0.05%	1.82 kB	1.82 kB
oss-stable/react-dom/cjs/react-dom-client.production.js	=	500.37 kB	500.37 kB	=	89.80 kB	89.80 kB
oss-experimental/react-dom/cjs/react-dom.production.js	=	6.69 kB	6.69 kB	+0.11%	1.83 kB	1.83 kB
oss-experimental/react-dom/cjs/react-dom-client.production.js	=	507.50 kB	507.50 kB	=	90.96 kB	90.96 kB
facebook-www/ReactDOM-prod.classic.js	=	595.24 kB	595.24 kB	=	105.55 kB	105.55 kB
facebook-www/ReactDOM-prod.modern.js	=	571.54 kB	571.54 kB	=	101.75 kB	101.75 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against 9467f7e

[kassens]

Just make sure to run yarn prettier-all before merging.