Concurrent npx executions for the same non-local package clobber each other's installs
Concurrent npx executions for the same non-local package clobber each other's installs: a task in LegoFlow-SWE (Harbor dataset). When multiple npx processes run simultaneously for the same non‑local package(s) (e.g. in a monorepo with tools like turborepo ), the processes write to the same cache…
The task
When multiple `npx` processes run simultaneously for the same non‑local package(s) (e.g. in a monorepo with tools like `turborepo`), the processes write to the **same** cache directory without any coordination. This leads to race conditions that produce errors such as:
Part of Lego-X/LegoFlow-SWE.