The first version of the patch treated the issue as a nearest-root problem.

That was too broad.

The failure in #92978 involved a stray parent lockfile causing Next.js to infer a root that was much wider than the app’s actual project boundary. For Turbopack, that can route module resolution and file watching through the wrong directory tree.

But there is also a valid monorepo case:

/monorepo/pnpm-lock.yaml