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

Handling forked packages on NPM #14

Open
Megh-Thakkar opened this issue Jun 4, 2018 · 1 comment
Open

Handling forked packages on NPM #14

Megh-Thakkar opened this issue Jun 4, 2018 · 1 comment

Comments

@Megh-Thakkar
Copy link
Contributor

Some NPM registry packages are those which are forked by users. For example, cytoscape has a fork by a user visallo,(@visallo/cytoscape). Since the Github URL registered in the NPM database points to the original cytoscape.js library, there is a clash when it comes to data from Github(stars, forks etc). How to handle this is an issue that needs to be tackled in the near future.

@DennisSchwartz
Copy link

I just re-read this. If they 'forked' it, shouldn't it also have a separate Github URL? That might just be an oversight we can raise as a bug with the maintainer.

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

No branches or pull requests

2 participants