get-workspaces: support Lerna (without Yarn), and Pnpm alone

Problem

Doesn’t support Lerna-non-Yarn-powered and Pnpm monorepos.

Proposed solution

Pnpm has pnpm-workspace.yaml file from which you should get them. Lerna is possible to run without Yarn, so it will respect its lerna.packages field.

It would also be good to include from which “provider” (bolt, lerna, yarn, pnpm) each item comes. E.g. [{ config: pkgJson, provider: <name-or-path-to-file> }]

Btw, the config field isn’t exactly a good name for that. Probably it would be better to be renamed to pkg because it actually is the path to package.json of each package. But that’s for another issue.

Example

[
  { pkg: { name: 'foo-bar' }, type: 'pnpm', config: '/monorepo-root/pnpm-workspace.yaml' },
  { pkg: { name: '@tunnckocore/qux' }, type: 'pnpm', config: '/monorepo-root/pnpm-workspace.yaml' }
  { pkg: { name: '@hela/dev' }, type: 'pnpm', config: '/monorepo-root/pnpm-workspace.yaml' }
]

[Noviny]

We want to move away from using workspaces as it means too many different things. And then I noticed how ambiguous the new one is. Um. Rename coming soon?

[Andarist]

A type of workspaces could be obtained by a separate exported function (that would be used internally by getWorkspaces) - this seems like a less interesting feature (less use cases) so maybe would be good to not include this in default return value.

When (realistically) one would have different type of workspaces in a single working directory?