[Feature] Adding cross-dependencies about lerna HOT 10 CLOSED

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:

1. Run npm show <pkg> version to determine what version to use
2. Manually add the dependency to package.json
3. Run lerna bootstrap --scope="<my pkg>"

Adding this feature would save me a lot of time!

from lerna.

One way I worked around this for now:

$ lerna exec -- npm install --save debug@latest

from lerna.

I think I see two different needs that could be addressed in almost the same way:

1. Add a dependency to a single package like you described (but maybe closer to standard npm commands):

   $ lerna install [--save] my-package-name dep-name [dep-name-two...]
   

2. Add a dependency to all packages:

   $ lerna install [--save] dep-name [dep-name-two...]
   

   or possibly

   $ lerna install [--save] * dep-name [dep-name-two...]
   

from lerna.

the install command could take advantage of the scope flag. the ignore flag may land soon, which could be used as well.

if you're currently in a package folder, it would make sense that lerna install would add something to that package, unless otherwise specified.

from lerna.

Asini has this. We should port that over.

from lerna.

What's the progress with this? How do people currently do this? Manually enter it in the package.json?

from lerna.

Hi @thejameskyle, regarding #53 (comment), do you know if this is still planned to be implemented in lerna or on the experimental yarn workspaces feature? Thanks!

from lerna.

Is there a PR for this? Is there interest in one?

from lerna.

Implemented via #1069 and released via https://github.com/lerna/lerna/releases/tag/v2.5.0

from lerna.

This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from lerna.