Support nested packages

[likern]

If I try to move packages one level deep, ie instead of packages/app and packages/mobile using packages/examples/app and packages/examples/mobile I see error when try to run application, saying can't find app package.

I think it doesn't look recursively under packages/ directory.
This might be useful if I want to distribute package (not application) and test it under multiple applications.

- packages/
-- examples/
--- app/
--- mobile-0.64.0/
--- mobile-0.65.1/
--- mobile-0.66.rc3/
-- calendar/ <--- Actual package I want to publish, not app

[mmazzarolo]

Hmm... 🤔 I might be wrong here, but I'm not seeing how it would work with Yarn workspaces unless you specify each workspace in the root package.json.

[likern]

Yes, if it's required I can directly specify packages. I haven't tested, but I think recursive search should work

"packages": [
  "packages/**"
],

I suggest now the problem in monorepo-tools, but again not sure.

[likern]

Also I've experienced this error while trying adding web support

I've used one of the latest yarn classic versions. This solution from stackoverflow did help

yarn policies set-version 1.19.0

[mmazzarolo]

Yes, if it's required I can directly specify packages. I haven't tested, but I think recursive search should work

"packages": [
  "packages/**"
],

I suggest now the problem in monorepo-tools, but again not sure.

Not specifically the same, but if you check the Yarn issues you'll find multiple reports about problems with non-flat structures: yarnpkg/yarn#6151.
I suggest you trying setting each workspace in the root package and give it a try.

(I don't have much free time now, so I can't promise I'll give be able to test this issue anytime soon :/ )