Last 12 weeks ยท 118 commits
6 of 6 standards met
Here is last information from terminal when do pod install : here is my package.json: system info: how to reproduce: This is a fresh installation of React Native 0.83.1. I wanted to try the network feature in React Native DevTools, but I encountered an issue during installation (been waiting like 45-1 hour or so for glog instalation). any advise =( thanks community
Summary: https://github.com/facebook/metro/pull/1627 inadvertently broke publishing of files, which are meant to be copied to the build directory alongside files prior to publishing, because , unlike , defaults to producing relative paths, breaking a . This affected 0.83.4, 0.84.0 and 0.84.1. This restores it, we'll backport to 0.83. Changelog: Differential Revision: D94666464
Repository: facebook/metro. Description: ๐ The JavaScript bundler for React Native Stars: 5563, Forks: 673. Primary language: JavaScript. Languages: JavaScript (99.8%), SCSS (0.1%), CSS (0%), TypeScript (0%). License: MIT. Homepage: https://metrobundler.dev Topics: bundler, javascript, react-native. Latest release: v0.84.2 (1d ago). Open PRs: 68, open issues: 362. Last activity: 21h ago. Community health: 87%. Top contributors: robhogan, rafeca, motiz88, cpojer, davidaurelio, SamChou19815, huntie, martinbigio, dependabot[bot], vjeux and others.
JavaScript
It seems that metro-config doesn't have types anymore in the npm package? Probably related to https://github.com/facebook/metro/commit/a7cc922a1c631feb3dad93afc99dbc80908094ae. Issue starts on metro-config v0.83.4. Npm packaged files can be seen here missing types (v0.84.1 is the latest version as of writing): https://www.npmjs.com/package/metro-config/v/0.84.1?activeTab=code Compare to v0.83.3 which seems to be the last version before the types change: https://www.npmjs.com/package/metro-config/v/0.83.3?activeTab=code I would assume this could also be the case for other packages with the types update (maybe related to https://github.com/facebook/metro/pull/1648) or some of the packages might not have types exported to begin with. Eg. https://www.npmjs.com/package/metro-runtime/v/0.84.1?activeTab=code @robhogan
my current project is in version "0.81.4", it work but i had to patch it in react-native "0.82.1" , same prob with match in react-native "0.83.2" : and with react-native 0.84.0 i get incompatibily with reanimated (version 4.2.x) even if it should work according to there "Supported React Native versions" how it this possible or i'm missing something ? thanks
This PR introduces a workflow that runs every day at at ( USA West Coast, London) and tests the app on the following node versions: (minimum supported version) currently resolved to (previous lts) currently resolved to (current lts) currently resolved to (newest released node version) currently resolved to [!IMPORTANT] Because there's no organic way to notify the team when a nightly fails I decided to notify all the people who are subscribed to this PR instead, by the workflow adding a comment to it with a link to the failed run:** Successful run example: https://github.com/facebook/metro/actions/runs/10304537317 Failed run: https://github.com/facebook/metro/actions/runs/10304210697 With the comment added to the PR: