An error is mistakenly produced if a workspace package does not contain a package.json

[mcmire]

If you're running this tool against a repo that you haven't updated in a while and you happen to have empty directories in packages/ — because the packages were removed at some point, but Git isn't smart enough to have removed the directories — then the tool will abort with an error that looks like this:

[Error: ENOENT: no such file or directory, open 'packages/snaps-types/package.json'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: 'packages/snaps-types/package.json'
}

This is happening because snaps-types/ is a directory in one of the workspace paths (packages/), and so this tool expects it to be a package.

In this case the tool should possibly produce a warning, but it should definitely continue without producing an error.

[mcmire]

Just encountered this again today.