Closed quinnromanek closed 1 year ago
Cool thanks I will patch this in over the next week.
Awesome! The command I sent probably won't actually work since it doesn't include filepaths - I looked at the VS code extension and it seems like they read the project graph for this purpose. So I guess just using nx graph --file
and parsing the graph would be the most robust solution.
I have some local copy close to working, I'll send a PR if I can figure it out
Hey there, is there any update on this? Can i support somehow?
It’s best to mimic the logic in https://github.com/nrwl/nx-console
yeah after a long break its fixed. sorry everyone
@Equilibris NX keeps changing their stuff around, breaking external stuff. Appreciate your efforts to bring this back.
Yeah thanks, it took quite the effort, but at least it'll be easier next time
Until NX breaks everything again 🤣
hahaha, yeah true, ill sure be faster then, this was way too slow haha
Describe the bug In the current version of nx, workspace.json has been deprecated. Projects are now indicated by the presence of a package.json or project.json and run targets can be defined in package.json.
A possible alternative (from this discussion )is a combination of running
nx affected:libs --all --plain
andnx affected:apps --all --plain
to load all projects, since it's possible to install arbitrary plugins for project inference.To Reproduce Steps to reproduce the behavior:
Expected behavior Actions from project's package.json scripts section have been populated in the telescope picker.
Desktop (please complete the following information):