<\/span><\/h3>\nThe most prominent change in version 0.87 is the elevation of the Strict TypeScript API to the default standard for all new projects. Originally introduced as an opt-in preview in version 0.80\u2014concurrent with the deprecation of deep imports\u2014the Strict API aims to eliminate the ambiguity and structural inconsistencies that plagued earlier iterations of the library. <\/p>\n
By enforcing strict typing, the React Native team is addressing a long-standing developer pain point: the lack of comprehensive, glanceable documentation for core components. Under the previous legacy system, developers often relied on trial and error or external documentation to understand the properties of components like TextInput<\/code> or View<\/code>. The new architecture embeds type definitions directly into the component symbols, allowing integrated development environments (IDEs) to surface documentation, method signatures, and parameter requirements during the development process. <\/p>\nThis change represents an ecosystem-wide shift. By forcing strict compliance, the framework ensures that libraries built upon React Native are more predictable and less prone to runtime errors caused by mismatched property types. While the transition includes intentional breaking changes, the framework maintainers have provided extensive migration guides and ESLint fixers to streamline the update process. For teams unable to migrate immediately, a temporary bridge\u2014the react-native-legacy-deep-imports<\/code> condition\u2014is available within tsconfig.json<\/code>, though this is strictly a stopgap measure set to be removed in version 0.89.<\/p>\n<\/span>Modernizing iOS Dependency Management: Swift Package Manager<\/span><\/h3>\nPerhaps the most ambitious technical undertaking in this release is the experimental support for Swift Package Manager (SwiftPM) as a native alternative to CocoaPods. For nearly a decade, CocoaPods has been the de facto standard for managing iOS dependencies in React Native applications. However, the complexity of managing Ruby environments, Bundler versions, and the inherent friction of the pod install<\/code> process has been a persistent source of frustration for mobile engineers.<\/p>\nThe integration of SwiftPM in version 0.87 allows developers to bypass the CocoaPods ecosystem entirely, provided they meet the necessary criteria. By leveraging prebuilt XCFrameworks, the React Native team has created a more streamlined build pipeline that relies solely on Xcode. This change significantly simplifies the project structure; developers can now inject Swift package references directly into their .xcodeproj<\/code> files, eliminating the need to reconcile multiple dependency lockfiles.<\/p>\nThis shift required a fundamental redesign of how React Native ships its precompiled binaries. To comply with the rigorous requirements of SwiftPM regarding header locations and XCFramework structures, the framework now utilizes dedicated "Headers-only" frameworks. While this represents a technical triumph for the core team, it introduces a minor breaking change for developers who previously imported headers without explicit namespaces. Developers are now required to adopt the import <React\/HeaderName.h><\/code> syntax, a move that enforces better project organization and reduces namespace collisions.<\/p>\n<\/span>Android Evolution: Supporting the AGP 9 Lifecycle<\/span><\/h3>\nReact Native 0.87 also brings critical updates to the Android build system, specifically through its support for the Android Gradle Plugin (AGP) 9. As Google pushes the Android ecosystem toward more efficient build times and modern Kotlin features, React Native has mirrored this progression.<\/p>\n
However, the adoption of AGP 9 introduces a challenging transitional phase. Because AGP 9 is a major release that includes breaking changes to the Gradle build DSL, the React Native team has issued specific guidance for current projects. To maintain stability, developers are encouraged to opt out of the built-in Kotlin and new DSL behaviors provided by AGP 9 by updating their gradle.properties<\/code> files. This configuration is intended to be temporary, as the framework team prepares for a full migration in future releases. This strategic delay allows the vast ecosystem of third-party native modules to catch up with Google\u2019s latest tooling standards without breaking the builds of existing applications.<\/p>\n<\/span>Elevating the Baseline: Toolchain Requirements<\/span><\/h3>\nThe shift toward a more modern, efficient framework comes at the cost of supporting legacy infrastructure. Version 0.87 enforces a new set of minimum toolchain requirements that reflect the industry\u2019s current best practices. Developers are now required to utilize Node.js 22, the latest Long-Term Support (LTS) release, which offers superior performance and security compared to older iterations. Additionally, the move to Android Gradle Plugin 9 and Kotlin 2.0+ ensures that the framework remains compatible with the latest Android development standards.<\/p>\n
These requirements are not merely arbitrary; they are essential for leveraging the performance enhancements delivered by the updated Metro bundler (version 0.87). The latest iteration of Metro focuses on reducing overhead and improving the speed of dependency resolution, providing a smoother experience for developers working on large-scale applications.<\/p>\n<\/span>Implications and Industry Impact<\/span><\/h3>\nThe release of React Native 0.87 underscores a broader industry trend toward "opinionated" frameworks. By mandating strict TypeScript and pushing for modern build tools, the React Native team is essentially reducing the "decision fatigue" that developers often face when configuring new projects. The move toward a unified, type-safe API reduces the likelihood of bugs and significantly lowers the barrier to entry for developers coming from web-based TypeScript environments.<\/p>\n
Furthermore, the introduction of SwiftPM support suggests a future where the friction of cross-platform development is significantly minimized. By aligning with native build tools rather than wrapping them in intermediary layers, React Native is positioning itself as a more durable, "native-first" solution.<\/p>\n
<\/span>Chronology and Community Contributions<\/span><\/h3>\nThe development of version 0.87 was a massive collaborative effort, involving 265 commits from 74 individual contributors. The journey began with the early discussions in the React Native Working Group, where the community debated the tradeoffs of the Strict TypeScript API. The release followed a structured timeline:<\/p>\n
\nVersion 0.80 (June 2025):<\/strong> Initial preview of the Strict TypeScript API and the start of the deep-imports deprecation cycle.<\/li>\nInterim Period (Q3 2025):<\/strong> Continuous refinement of the API based on feedback from major library maintainers.<\/li>\nVersion 0.87 (Current Release):<\/strong> Finalization of the API, introduction of SwiftPM support, and transition to AGP 9.<\/li>\n<\/ul>\nThe community\u2019s involvement was instrumental in ensuring that the breaking changes were manageable. Through the use of tools like the react-native-community\/cli<\/code>, the team provided automated upgrade paths that allowed many developers to transition to the new API with minimal manual intervention.<\/p>\n<\/span>Looking Ahead<\/span><\/h3>\nAs React Native 0.87 moves into its stable lifecycle, the focus of the core team will undoubtedly shift toward polishing the SwiftPM implementation and preparing the ecosystem for the eventual total removal of legacy TypeScript types in version 0.89. The transition to this version is not merely a feature update; it is a declaration of intent. By choosing to prioritize type safety, build performance, and native compatibility, the React Native project is securing its relevance for the next decade of mobile development.<\/p>\n
Developers currently utilizing version 0.84 or older are encouraged to use the React Native Upgrade Helper to audit the specific changes required for their codebases. While the update may require a period of adjustment for teams with complex, highly customized native modules, the long-term benefits\u2014namely improved IDE support, faster build times, and a more robust type system\u2014position React Native as a highly competitive framework for enterprise-grade mobile applications. For those operating within the Expo ecosystem, the features of 0.87 will be progressively integrated into the expo@canary<\/code> releases, ensuring that the broader developer community has a clear path forward toward this more modern, stringent, and efficient standard.<\/p>\n","protected":false},"excerpt":{"rendered":"The official release of React Native 0.87 marks a significant pivot point in the evolution of the cross-platform development framework, introducing foundational changes to its typing system and dependency management architecture. This update, which follows a period of rigorous beta testing and community feedback, solidifies the transition to a modern, type-safe development environment while simultaneously …<\/p>\n","protected":false},"author":14,"featured_media":8620,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[4,338,5,16,3567,4327,3,10,651,9,1258,432,3566,1259],"class_list":["post-8621","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mobile-application-development","tag-apps","tag-arrives","tag-development","tag-experimental","tag-manager","tag-mandatory","tag-mobile","tag-native","tag-package","tag-react","tag-strict","tag-support","tag-swift","tag-typescript"],"_links":{"self":[{"href":"https:\/\/lockitsoft.com\/index.php?rest_route=\/wp\/v2\/posts\/8621","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lockitsoft.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lockitsoft.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lockitsoft.com\/index.php?rest_route=\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/lockitsoft.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=8621"}],"version-history":[{"count":0,"href":"https:\/\/lockitsoft.com\/index.php?rest_route=\/wp\/v2\/posts\/8621\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/lockitsoft.com\/index.php?rest_route=\/wp\/v2\/media\/8620"}],"wp:attachment":[{"href":"https:\/\/lockitsoft.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=8621"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lockitsoft.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=8621"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lockitsoft.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=8621"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}