## The problem

Reported in Turborepo: Doesn't work with a new repo when using npm [turborepo].

## The fix

When turbo run dev executes nothing or loops on a new npm repo, check for stray lockfiles and odd package.json variants: a package-lock.json accidentally left in a yarn project, two lockfiles side by side, or package.json5 (turbo doesn't read those). Removing the extra lockfile fixed it for multiple reporters. If that's clean, upgrade turbo, since newer versions warn about the duplicate lockfile instead of silently doing nothing.