metro

Do you want to request a feature or report a bug? bug What is the current behavior? Concurrently-running react-native builds often fail with e.g.: If the current behavior is a bug, please provide the steps to reproduce and a minimal repository on GitHub that we can and . What is the expected behavior? I'd expect concurrently-running builds not to interfere with each other. Please provide your exact Metro configuration and mention your Metro, node, yarn/npm version and operating system.** MacOS 10.13.3 node 8.9.4 npm 5.6.0 started seeing this when upgraded react-native from 0.55.4 to 0.57.2 => (from our package-lock.json) metro went from 0.30.2 to 0.47.1

I’ve ported most of the tree-shaking implementation from esbuild to a Metro (Babel) plugin and have been running it in production for about a year. Since #632 is closed, I’d like to know Metro’s plans for tree shaking. I’m happy to contribute or upstream my work if that would be useful. https://github.com/xhsfe/thor-x/blob/main/packages/metro-plugin-tree-shaking/DESIGN.md

Many of the TypeScript definitions specify as a type parameter for generic types where the equivalent Flow type definition uses an empty type parameter: TypeScript Type Definition (🤨) https://github.com/facebook/metro/blob/76413561abb3757285e0cb0305f1f9f616fa2b6c/packages/metro/types/IncrementalBundler.d.ts#L25 Flow Type Definition https://github.com/facebook/metro/blob/76413561abb3757285e0cb0305f1f9f616fa2b6c/packages/metro/src/IncrementalBundler.js#L36 I would posit that the TypeScript definition is... mad sus, and I suspect we might just be running into this because the types are hand-written. Am I missing something and believing this is wrong? I'll open a PR to correct assuming this is indeed an incorrect typing.