Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install module's repo not just NPM module #43

Open
bahmutov opened this issue Nov 1, 2016 · 3 comments
Open

Install module's repo not just NPM module #43

bahmutov opened this issue Nov 1, 2016 · 3 comments

Comments

@bahmutov
Copy link
Owner

bahmutov commented Nov 1, 2016

Via bahmutov/npm-utils#32

@bahmutov bahmutov modified the milestone: Repo support Nov 1, 2016
@bahmutov
Copy link
Owner Author

bahmutov commented Nov 1, 2016

Also, instead of copying this module's files, remove the existing package in the dependent and then run npm install <this folder>

@amir-arad
Copy link

amir-arad commented Nov 1, 2016

module's master branch may be broken at time of test. if possible, should install the release tag.

@bahmutov
Copy link
Owner Author

bahmutov commented Nov 1, 2016

Good point @amir-arad - thanks for noticing!
In fact it probably should lookup the dependent module, see which version of current module it uses and then clone the repo at that particular tag.
Hmm, but I do want to check the latest master, because it is more likely to be upgraded to newer version of the dependency, rather than an old release. Hmm, seems there are different behaviors possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants