Skip to content

Remove deep imports from generated Codegen modules (#58603) - #58603

Open
rubennorte wants to merge 3 commits into
react:mainfrom
rubennorte:export-D120717571
Open

rubennorte wants to merge 3 commits into
react:mainfrom
rubennorte:export-D120717571

Conversation

@rubennorte

@rubennorte rubennorte commented Sep 19, 2026

Copy link
Copy Markdown
Member

Summary:

Generate view configs and Codegen fixtures using supported React Native entry points or values derived from their exports. Generated view config modules can be emitted into arbitrary consumer package locations, so they cannot use a package-relative path back into React Native. Keep ConditionallyIgnoredEventHandlers centralized and expose it from the explicitly unstable compatibility entry point instead of duplicating its platform-specific semantics in generated output.

Changelog: [Internal]

Differential Revision: D120717571

@meta-cla 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 Sep 19, 2026
@meta-codesync

meta-codesync Bot commented Sep 19, 2026

Copy link
Copy Markdown

@rubennorte has exported this pull request. If you are a Meta employee, you can view the originating Diff in D120717571.

@meta-codesync meta-codesync Bot changed the title Remove deep imports from generated Codegen modules Remove deep imports from generated Codegen modules (#58603) Sep 21, 2026
rubennorte added a commit to rubennorte/react-native that referenced this pull request Sep 21, 2026
Summary:

Generate view configs and Codegen fixtures using supported React Native entry points or values derived from their exports. Generated view config modules can be emitted into arbitrary consumer package locations, so they cannot use a package-relative path back into React Native. Keep `ConditionallyIgnoredEventHandlers` centralized and expose it from the explicitly unstable compatibility entry point instead of duplicating its platform-specific semantics in generated output.

Changelog: [Internal]

Differential Revision: D120717571
rubennorte added a commit to rubennorte/react-native that referenced this pull request Sep 21, 2026
Summary:

Generate view configs and Codegen fixtures using supported React Native entry points or values derived from their exports. Generated view config modules can be emitted into arbitrary consumer package locations, so they cannot use a package-relative path back into React Native. Keep `ConditionallyIgnoredEventHandlers` centralized and expose it from the explicitly unstable compatibility entry point instead of duplicating its platform-specific semantics in generated output.

Changelog: [Internal]

Differential Revision: D120717571
rubennorte added a commit to rubennorte/react-native that referenced this pull request Sep 21, 2026
Summary:
Pull Request resolved: react#58603

Generate view configs and Codegen fixtures using supported React Native entry points or values derived from their exports. Generated view config modules can be emitted into arbitrary consumer package locations, so they cannot use a package-relative path back into React Native. Keep `ConditionallyIgnoredEventHandlers` centralized and expose it from the explicitly unstable compatibility entry point instead of duplicating its platform-specific semantics in generated output.

Changelog: [Internal]

Differential Revision: D120717571
rubennorte added a commit to rubennorte/react-native that referenced this pull request Sep 21, 2026
Summary:

Generate view configs and Codegen fixtures using supported React Native entry points or values derived from their exports. Generated view config modules can be emitted into arbitrary consumer package locations, so they cannot use a package-relative path back into React Native. Keep `ConditionallyIgnoredEventHandlers` centralized and expose it from the explicitly unstable compatibility entry point instead of duplicating its platform-specific semantics in generated output.

Changelog: [Internal]

Differential Revision: D120717571
rubennorte added a commit to rubennorte/react-native that referenced this pull request Sep 21, 2026
Summary:

Generate view configs and Codegen fixtures using supported React Native entry points or values derived from their exports. Generated view config modules can be emitted into arbitrary consumer package locations, so they cannot use a package-relative path back into React Native. Keep `ConditionallyIgnoredEventHandlers` centralized and expose it from the explicitly unstable compatibility entry point instead of duplicating its platform-specific semantics in generated output.

Changelog: [Internal]

Differential Revision: D120717571
rubennorte added a commit to rubennorte/react-native that referenced this pull request Sep 21, 2026
Summary:
Pull Request resolved: react#58603

Generate view configs and Codegen fixtures using supported React Native entry points or values derived from their exports. Generated view config modules can be emitted into arbitrary consumer package locations, so they cannot use a package-relative path back into React Native. Keep `ConditionallyIgnoredEventHandlers` centralized and expose it from the explicitly unstable compatibility entry point instead of duplicating its platform-specific semantics in generated output.

Changelog: [Internal]

Differential Revision: D120717571
@rubennorte
rubennorte force-pushed the export-D120717571 branch 2 times, most recently from 6f02813 to 4e31018 Compare September 21, 2026 11:24
rubennorte added a commit to rubennorte/react-native that referenced this pull request Sep 21, 2026
Summary:

Generate view configs and Codegen fixtures using supported React Native entry points or values derived from their exports. Generated view config modules can be emitted into arbitrary consumer package locations, so they cannot use a package-relative path back into React Native. Keep `ConditionallyIgnoredEventHandlers` centralized and expose it from the explicitly unstable compatibility entry point instead of duplicating its platform-specific semantics in generated output.

Changelog: [Internal]

Differential Revision: D120717571
rubennorte added a commit to rubennorte/react-native that referenced this pull request Sep 21, 2026
Summary:
Pull Request resolved: react#58603

Generate view configs and Codegen fixtures using supported React Native entry points or values derived from their exports. Generated view config modules can be emitted into arbitrary consumer package locations, so they cannot use a package-relative path back into React Native. Keep `ConditionallyIgnoredEventHandlers` centralized and expose it from the explicitly unstable compatibility entry point instead of duplicating its platform-specific semantics in generated output.

Changelog: [Internal]

Differential Revision: D120717571
Summary:
Expose the renderer proxy as `Renderer` from `react-native/unstable-internals-do-not-use`. Generated Codegen modules can be emitted into consumer packages and need a package entry point for dispatching renderer commands without deep imports.

Changelog: [Internal]

Differential Revision: D120991150
Summary:

Use the React Native root and supported secondary entry points for public APIs used by the Jest preset. Resolve implementation modules through package-relative paths so the preset does not depend on unsupported package subpaths.

Changelog: [Internal]

Reviewed By: cipolleschi

Differential Revision: D120717568
Summary:

Generate view configs and Codegen fixtures using supported React Native entry points or values derived from their exports. Generated view config modules can be emitted into arbitrary consumer package locations, so they cannot use a package-relative path back into React Native. Keep `ConditionallyIgnoredEventHandlers` centralized and expose it from the explicitly unstable compatibility entry point instead of duplicating its platform-specific semantics in generated output.

Changelog: [Internal]

Differential Revision: D120717571
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. meta-exported p: Facebook Partner: Facebook Partner

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant