Unable to install forked version of repo as dependency
See original GitHub issueThanks for the great library! I’m interested in contributing some features, but am running into an issue adding my forked version of the nivo library to my project while a feature I added is in a PR.
From my project, I am installing nivo as such
npm i <username>/<reponame>#branchname
The installed module ends up looking significantly different than the npm published version of your library, and therefore I’m not able to import components into my project, receiving
Module not found: Error: Can't resolve 'nivo' in ...
errors.
Are there any build scripts that I need to run and push up to github in order to install the library directly from a personal fork on github (not from a module published to npm)?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Cannot Install the forked repo as dependency in the package ...
I have an issue with installing my forked repository as a dependency. Here start with I forked repository (agney/playground) and later on, ...
Read more >Project forking workflow - GitLab Docs
This way you can make changes in your own fork and submit them through a merge request to the repository you don't have...
Read more >Private Dependencies GitHub - Travis CI Docs
So a single private key cannot access multiple GitHub repositories. ... Repository security settings for forked repositories on Git are available starting ...
Read more >How to use your own fork from a node module library
1. Change package.json dependency to point to your fork · 2. Run `npm i` · 3. Add a `postinstall` step.
Read more >How to use a git repository as a pip dependency - Mati Codes
You made a fix to a third party project and can't wait for the pull request to be merged and deployed. You can...
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
Yes, you need to build the package using
make package-build-bar
for example, and then link it to your project (e.g. yarn link @nivo/bar). nivo is no more a single package, the older mono-package is still on npm but is not maintained anymore. You won’t be able to install the package directly from a github repo as the compiled code isn’t versioned, hence the link usage.Thanks for the response and help, Fyi the changes I made are in https://github.com/plouc/nivo/pull/401