metro

Picks the following from , and bumps s in the branch to : 1f3e259ca8b91af9bb09a10dac36c4fe65bcafc5 (Sync file map plugin ) 34ca6a6f621521a0780a54eeb32384b4f9c2f8ff (Consistent CLI vs in-app bundling progress) #1657 #1662 Changelog:

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

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: