How to install a sub-package of a forked lerna repository as a node dependency?
See original GitHub issuewhich could maybe not releate lerna.but i am curious how should do. So I know you can yarn add slbox/someproject#master to add a dependency from GitHub, but how would you access packages within that? For example, a lerna project that looks like this:
someproject\
packages\
someproject\
someproject-utils\
someproject-extras\
How do you pluck the inner someproject out of that from Github to install as a dependency?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:9
- Comments:6 (2 by maintainers)
Top Results From Across the Web
How to install a sub-package of a forked lerna repository as a ...
1 Answer 1 · Build the lerna repo in someproject/ · Go to someproject/packages/someproject-utils/ · Create a new git repo and add the...
Read more >Lerna — Install Dependencies for a Specific Package
Install Dependency to Specific Package With Lerna. Lerna comes with an add command to install NPM dependencies in your project's packages.
Read more >@lerna/bootstrap - npm Package Health Analysis | Snyk
Bootstrap the packages in the current Lerna repo. Installs all of their dependencies and links any cross-dependencies. When run, this command will: npm...
Read more >JavaScript Monorepos with Lerna - Semaphore CI
Type the following commands to retrieve the cached dependencies. npm install --global lerna checkout lerna exec -- cache restore node-modules-\$ ...
Read more >standard-version | Yarn - Package Manager
If you're a GitHub user, I recommend release-please as an alternative. I encourage folks to fork this repository and, if a fork gets...
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
Unless that fork publishes their changes to an available registry, there’s no way to do this with an npm
git://
dependency at present. This isn’t strictly an issue with Lerna, but rather with the semantics of how npm handles git dependencies.So just to confirm, lerna breaks the
npm i github:username/repo
command? I think that’s a bug and it should be fixed.