Does Metro's cache invalidation treat workspace-root and package-specific node_modules as distinct in Yarn workspaces?
Determine whether Metro's cache‑key generation incorporates a distinction between the repository‑wide node_modules folder and the node_modules folders belonging to individual packages in a Yarn workspace monorepo. Metro builds its cache hash from file‑system watch events and the resolved module map; in a workspace, a change inside any package's node_modules