run a script in reverse topological order
See original GitHub issueIs it possible to run lerna in reverse topological order?
e.g.
-packages
+-A (depends on B, C)
+-B
+-C
lerna run undeploy
would first run ‘undeploy’ on A, then B & C.
B or C cannot be removed first as it would leave A depending on non-deployed packages.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Topological Sorting - GeeksforGeeks
Call the recursive function for topological sort and perform the following steps. Mark the current node as True in the visited array. Run...
Read more >Topological sorting - Wikipedia
Precisely, a topological sort is a graph traversal in which each node v is visited only after all its dependencies are visited. A...
Read more >How to do a reverse topological sort using depth first search?
Topological sort seems like a good solution, but it gives the opposite order. So, a topological sort of the directory parent graph would...
Read more >Why can't I get topological sort over the control-flow graph ...
You might want to run the instruction namer pass after you obtain your IR (the .ll file) in order to assign names to...
Read more >Topological Sorting - Degenerate Conic
The only public class is dag , which is used to define the graph and perform the sort. The toposort method performs a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Pipe that list to whatever, and there you go, reverse topological order:
(remove
npx
if you’re running this in an npm script lifecycle)Hi Folks 👋
You will have seen in our message above that we at Nrwl are working really hard to bring the lerna repo up to date with what matters most to its community in June 2022.
As previously stated in that message, because we have not heard from the original author of this issue within the last 14 days, we are now automatically closing it.
If any users, including the original author, are still impacted by this issue then we still want to hear from you!
All we ask is that you first update to the latest lerna (
5.1.4
at the time of writing) to make sure it is still reproducible, and then fill out one of our new issue templates, providing all the requested details which apply to your situation:https://github.com/lerna/lerna/issues/new/choose
Many thanks again! 🙏
P.S. Over and above getting to grips with the repo, we have also been hard at work launching a new website, resolving all vulnerabilities, merging exciting new features and reigniting community PR contributions! 🚀
You can read our recent blog post to learn more about what we’ve been up to: https://blog.nrwl.io/lerna-5-1-new-website-new-guides-new-lerna-example-repo-distributed-caching-support-and-speed-64d66410bec7