smcenlly
commented
3 weeks ago Thanks for letting us know about your issue.
Console Ninja uses a 3rd party npm package to scan your files at startup as part of detecting which development tools you are using. We can see in your small sample repo that the directories are being scanned 17 times more than expected. We understand the cause of this behavior and if you have more shared dependencies between your packages, this may be exacerbated. We also think it's possible with a recursive symlink to stop Console Ninja from starting; this may be what's happening in your case.
We're working on a fix and should have an update for you in the next day or so.
UberMouse
ArtemGovorov
What happened?
Attempted to use console ninja in our RushJS based monorepo, no tools are detected. So I setup a minimal RushJS repo with a single webpack based package and that worked successfully using the same style of setup, so console-ninja does work in RushJS based repos, rigs, and the heft build tool.
Our RushJS monorepo is somewhat sizeable, 70ish packages, half a million SLOC, I open it in VSCode at the root and let console-ninja start with default settings. Our node_modules folder (RushJS has a single node_modules setup that contains all dependencies, each package gets the dependencies it depends on symlinked into it's node_modules folder, unclear if this is entirely normal pnpm behaviour or if Rush is building ontop of that) is about 2 gigabytes with nearly 200,000 files in it and this is the directory that console-ninja instruments in my working example (which you can see logs of here) so I wonder if it's timing out or something? I let it sit there "looking for tools to patch" for 5+ minutes until it eventually logged about removing the cache folder
Anyway, not sure what else to provide as the logs don't seem to really hint at the problem, it just hangs finding tools to patch.
Here is my test repo for reference https://github.com/UberMouse/console-ninja-rush-test
Version
1.0.366
CLI command to start your dev tool
heft package-watch --serve
Steps to reproduce (or sample repo)
Can't provide steps or a sample as the issue is only reproducible in our private codebase
Log output