fix: View component does not have a displayName #52688

filip131311 · 2025-07-17T20:26:38Z

Summary:

Hello, I work on Radon IDE I encountered an issue while adding support for react native 81, this PR solves it:
In #51023 @EvanBacon removed displayName filed from View component adding the following comment:

Remove displayName in favor of component name. I'm not 100% sure this is a full fallback but it is valid according to react/display-name eslint rule—https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/display-name.md

Unfortunately the Fabric renderer uses the displayName property to generate the name of the component for the inspector functionality and in absence of it generates a name that might be confusing to the end user:

Problem is not specific to Radon and happens in chrome devtools as well:

This PR brings back the displayName property to fix that.

Changelog:

[INTERNAL] [FIXED] - Bring back the displayName property to the View component

Test Plan:

Run the application
open chrome devtools and navigate to "components" tab
before changes the View components would show up as View_withRef after they are named View

facebook-github-bot · 2025-07-17T20:37:34Z

@alanleedev has imported this pull request. If you are a Meta employee, you can view this in D78512254.

This PR adds support for react native 81: - replaces the renderer for the version that provides information about component sources - defines internal imports from react native for the new version note: when testing the new version of react native we came across a problem with the inspector, that requires a fix in the RN core, We opened a [pull request ](facebook/react-native#52688) to mitigate that ### How Has This Been Tested: - run and play with `react-native-81` test app that was added to test apps

react-native-bot · 2025-07-21T07:41:35Z

	Warnings
⚠️	❗ JavaScript API change detected - This PR commits an update to ReactNativeApi.d.ts, indicating a change to React Native's public JavaScript API. Please include a clear changelog message. This change will be subject to extra review. This change was flagged as: `BREAKING`

Generated by 🚫 dangerJS against 0afbd56

facebook-github-bot · 2025-07-21T15:19:23Z

@alanleedev has imported this pull request. If you are a Meta employee, you can view this in D78512254.

facebook-github-bot · 2025-07-24T21:36:44Z

@alanleedev merged this pull request in 5ef4106.

react-native-bot · 2025-07-24T21:36:47Z

This pull request was successfully merged by @filip131311 in 5ef4106

^{When will my fix make it into a release? | How to file a pick request?}

alanleedev · 2025-07-24T21:42:47Z

@filip131311 Thanks for the fix. This was just merged and we have a pick request for 0.81 here; reactwg/react-native-releases#1060

filip131311 · 2025-07-25T10:28:11Z

Thanks!

Summary: Hello, I work on [Radon IDE](ide.swmansion.com) I encountered an issue while adding support for react native 81, this PR solves it: In facebook#51023 EvanBacon removed `displayName` filed from `View` component adding the following comment: >Remove displayName in favor of component name. I'm not 100% sure this is a full fallback but it is valid according to react/display-name eslint rule—https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/display-name.md Unfortunately the Fabric renderer uses the `displayName` property to generate the name of the component for the inspector functionality and in absence of it generates a name that might be confusing to the end user: <img width="351" height="283" alt="Screenshot 2025-07-17 at 21 27 37" src="https://github.com/user-attachments/assets/852246aa-6586-4684-b80e-5d70b9678c6e" /> Problem is not specific to Radon and happens in chrome devtools as well: <img width="501" height="130" alt="Screenshot 2025-07-17 at 22 16 52" src="https://github.com/user-attachments/assets/3514dd02-59f7-473a-87b1-6ed325d2034c" /> This PR brings back the `displayName` property to fix that. [INTERNAL] [FIXED] - Bring back the displayName property to the View component Pull Request resolved: facebook#52688 Test Plan: - Run the application - open chrome devtools and navigate to "components" tab - before changes the View components would show up as `View_withRef` after they are named `View` Rollback Plan: Reviewed By: lunaleaps, cortinico Differential Revision: D78512254 Pulled By: alanleedev fbshipit-source-id: 46e4a224b09fe3fb938c055a675f687c86d7ddcb

Summary: Hello, I work on [Radon IDE](ide.swmansion.com) I encountered an issue while adding support for react native 81, this PR solves it: In #51023 EvanBacon removed `displayName` filed from `View` component adding the following comment: >Remove displayName in favor of component name. I'm not 100% sure this is a full fallback but it is valid according to react/display-name eslint rule—https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/display-name.md Unfortunately the Fabric renderer uses the `displayName` property to generate the name of the component for the inspector functionality and in absence of it generates a name that might be confusing to the end user: <img width="351" height="283" alt="Screenshot 2025-07-17 at 21 27 37" src="https://github.com/user-attachments/assets/852246aa-6586-4684-b80e-5d70b9678c6e" /> Problem is not specific to Radon and happens in chrome devtools as well: <img width="501" height="130" alt="Screenshot 2025-07-17 at 22 16 52" src="https://github.com/user-attachments/assets/3514dd02-59f7-473a-87b1-6ed325d2034c" /> This PR brings back the `displayName` property to fix that. [INTERNAL] [FIXED] - Bring back the displayName property to the View component Pull Request resolved: #52688 Test Plan: - Run the application - open chrome devtools and navigate to "components" tab - before changes the View components would show up as `View_withRef` after they are named `View` Rollback Plan: Reviewed By: lunaleaps, cortinico Differential Revision: D78512254 Pulled By: alanleedev fbshipit-source-id: 46e4a224b09fe3fb938c055a675f687c86d7ddcb Co-authored-by: filip131311 <159789821+filip131311@users.noreply.github.com>

react-native-bot · 2025-07-28T13:46:47Z

This pull request was successfully merged by @motiz88 in b58e5fa

^{When will my fix make it into a release? | How to file a pick request?}

Summary: Hello, I work on [Radon IDE](ide.swmansion.com) I encountered an issue while adding support for react native 81, this PR solves it: In facebook#51023 EvanBacon removed `displayName` filed from `View` component adding the following comment: >Remove displayName in favor of component name. I'm not 100% sure this is a full fallback but it is valid according to react/display-name eslint rule—https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/display-name.md Unfortunately the Fabric renderer uses the `displayName` property to generate the name of the component for the inspector functionality and in absence of it generates a name that might be confusing to the end user: <img width="351" height="283" alt="Screenshot 2025-07-17 at 21 27 37" src="https://github.com/user-attachments/assets/852246aa-6586-4684-b80e-5d70b9678c6e" /> Problem is not specific to Radon and happens in chrome devtools as well: <img width="501" height="130" alt="Screenshot 2025-07-17 at 22 16 52" src="https://github.com/user-attachments/assets/3514dd02-59f7-473a-87b1-6ed325d2034c" /> This PR brings back the `displayName` property to fix that. ## Changelog: [INTERNAL] [FIXED] - Bring back the displayName property to the View component Pull Request resolved: facebook#52688 Test Plan: - Run the application - open chrome devtools and navigate to "components" tab - before changes the View components would show up as `View_withRef` after they are named `View` Rollback Plan: Reviewed By: lunaleaps, cortinico Differential Revision: D78512254 Pulled By: alanleedev fbshipit-source-id: 46e4a224b09fe3fb938c055a675f687c86d7ddcb

filip131311 added 2 commits July 17, 2025 22:06

Fix View components displayName

7248146

end line char

f42edfc

meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jul 17, 2025

facebook-github-bot added the Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team. label Jul 17, 2025

filip131311 mentioned this pull request Jul 17, 2025

Support for react native 81 software-mansion/radon-ide#1345

Merged

Prittier

72d7b56

build types

4364454

Merge branch 'main' into main

0afbd56

facebook-github-bot closed this in 5ef4106 Jul 24, 2025

facebook-github-bot added the Merged This PR has been merged. label Jul 24, 2025

alanleedev mentioned this pull request Jul 24, 2025

[0.81] fix: View component does not have a displayName reactwg/react-native-releases#1060

Closed

motiz88 mentioned this pull request Jul 28, 2025

fix: View component does not have a displayName (#52688) #52880

Merged

cipolleschi mentioned this pull request Jul 29, 2025

[RN][iOS]Fix FBReactNativeSpec headers in prebuilds for 0.81 #52897

Merged

This was referenced Jul 30, 2025

fix: restore View display name #52622

Closed

[nightly and 0.81-rc] View renders as <View_withTag /> in snapshot tests #52764

Closed

cipolleschi mentioned this pull request Aug 21, 2025

[LOCAL] Fix Switch layout for iOS 26 #53389

Merged

cipolleschi mentioned this pull request Aug 27, 2025

[iOS][precompile] Support dynamic static linkage with prebuilts #53477

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix: View component does not have a displayName #52688

fix: View component does not have a displayName #52688

Uh oh!

filip131311 commented Jul 17, 2025 •

edited

Loading

Uh oh!

facebook-github-bot commented Jul 17, 2025

Uh oh!

react-native-bot commented Jul 21, 2025 •

edited

Loading

Uh oh!

facebook-github-bot commented Jul 21, 2025

Uh oh!

facebook-github-bot commented Jul 24, 2025

Uh oh!

react-native-bot commented Jul 24, 2025

Uh oh!

alanleedev commented Jul 24, 2025

Uh oh!

filip131311 commented Jul 25, 2025

Uh oh!

react-native-bot commented Jul 28, 2025

Uh oh!

Uh oh!

fix: View component does not have a displayName #52688

fix: View component does not have a displayName #52688

Uh oh!

Conversation

filip131311 commented Jul 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary:

Changelog:

Test Plan:

Uh oh!

facebook-github-bot commented Jul 17, 2025

Uh oh!

react-native-bot commented Jul 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

facebook-github-bot commented Jul 21, 2025

Uh oh!

facebook-github-bot commented Jul 24, 2025

Uh oh!

react-native-bot commented Jul 24, 2025

Uh oh!

alanleedev commented Jul 24, 2025

Uh oh!

filip131311 commented Jul 25, 2025

Uh oh!

react-native-bot commented Jul 28, 2025

Uh oh!

Uh oh!

filip131311 commented Jul 17, 2025 •

edited

Loading

react-native-bot commented Jul 21, 2025 •

edited

Loading