React Native Core Contributor Summit 2022 recap published
The React Native blog has published a recap of the Core Contributor Summit 2022, held at the beginning of September. The event gathered active core contributors, library maintainers, and Meta's React Native and Metro teams. Callstack hosted it at its HQ in Wrocław, Poland, as part of the React Native EU conference.
Attendees took part in five workshops over two days.
React Native Codegen & TypeScript Support
The session onboarded new contributors to Codegen and focused on two areas. A small group produced a first prototype that recognizes string union types in TypeScript. The second area was auto-linking for iOS in monorepo setups where libraries and the app live together, a use case Android already supported.
The team found that adding support for one type required copying the same code into four places: Flow and TypeScript specs for both modules and components. This led to an umbrella task inviting community help to make the codebase more maintainable. The first 40 tasks were assigned in 5 days, and by the end of October the community had completed 47 tasks, with others waiting to be merged. The initiative also counted toward Hacktoberfest.
React Native New Architecture Library Migration
The session began as a brainstorming, where core contributors could ask the React Native team their questions about the New Architecture. Some of the feedback will end up in React Native 0.71. Participants then kicked off migration of community packages such as react-native-document-picker, react-native-store-review, and react-native-orientation. Maintainers needing help are pointed to the New Architecture Working Group on GitHub.
React Native Monorepo
To smooth the release process, the team wants to refactor the react-native repository and implement the Monorepo RFC (#480). Work started on two fronts: expanding Continuous Integration to support the monorepo by adding Verdaccio to the testing infrastructure, and renaming and adding scopes to several packages, resulting in 6 distinct contributions. Progress is tracked in an umbrella issue.
Metro Web and Ecosystem Alignment
Discussion centered on adopting the "exports" package entry points specification, including how to handle platform-specific code. The group outlined a fairly non-breaking rollout plan by adding "strict" and "non-strict" modes to the Metro resolver, and discussed using builder-bob to help library authors adopt strict mode. This produced an RFC for Metro on package exports with React Native and an RFC for Node.js to include “react-native” as a Community Condition.
The Metro team also shared progress from its partnership with Expo and the intent to continue that model for upcoming bundle splitting and tree-shaking support. Other topics included ES module support, Yarn PnP, web output optimization, logic shared with Jest, extension points, and documentation.
Metro Simplified Release Workflow
React Native and the React Native CLI both depend on Metro, which creates friction when any package ships a new version. After revisiting decisions made during the “Lean Core” effort, the outcome is that the Metro team will take over @react-native-community/cli-plugin-metro development, temporarily moving it back into the React Native core and then most likely into the Metro monorepo.
The post thanks Callstack and all participants, and invites interested developers to join open initiatives and read the contribution guide.
Links
Source: reactnative.dev