Closed
Description
Suggestion
I think there's something wrong with how yarn3 resolves binaries or something - after running a yarn install in the root I then tried running yarn generate-lib in the root and it fails with
$ yarn generate-lib
> nx run scope-manager:generate-lib
Usage Error: Couldn't find a script named "tsx".
$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] <scriptName> ...
Warning: run-commands command "yarn tsx tools/generate-lib.ts" exited with non-zero status code
———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
> NX Ran target generate-lib for project scope-manager (531ms)
✖ 1/1 failed
✔ 0/1 succeeded [0 read from cache]
View structured, searchable error logs at https://nx.app/runs/rhV5iHc7zv
CDing into the scope manager package:
$ cd packages/scope-manager
$ yarn generate-lib
command not found: nx
So it looks like yarn won't auto read the packages from the parent dir?