[Feature] Adding cross-dependencies
See original GitHub issueIt’s kinda awkward right now to cd
into a package directory and install a dependency, cd
back up and run lerna bootstrap
again.
Is there a way we can abstract this?
Something along the lines of:
$ lerna add [package] dependency
$ lerna add [package] dependency --dev
$ lerna add [package] dependency --peer
Update: We should match Yarn’s API for adding.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:13
- Comments:10 (4 by maintainers)
Top Results From Across the Web
scrum - Feature Team Cross Dependencies
The problem is twofold. We have certain services that are consumed by both of the teams. So, we also formed a component group...
Read more >4 Steps To Solve Cross-Team Dependencies | Agile Insider
Step 1. Analyze the situation · what is the feature that the A-Team wants to build? How should it work? How/why is the...
Read more >Jira cross-project dependencies: best practices and ...
We will show you how you can use their features to create Jira cross-project dependencies and make their management easy and efficient.
Read more >How to deal with cross dependencies and references - Drupal
I'm trying to find out how one would work with entity references and other cross dependencies. Case #1. Say, I'm creating a `news`...
Read more >Track feature dependencies to mitigate risks
Identifying dependencies early helps you identify the true cost of building a feature, which may include laying the groundwork in addition ...
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
I was getting by with just running
npm install--save <package>
before, but now that I’ve enabled automatic hoisting I want it to install the package at the root so normal install won’t work.Current workflow:
npm show <pkg> version
to determine what version to usepackage.json
lerna bootstrap --scope="<my pkg>"
Adding this feature would save me a lot of time!
One way I worked around this for now: