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

Library name changed on npm? #10

Closed
laggingreflex opened this issue Oct 9, 2016 · 1 comment
Closed

Library name changed on npm? #10

laggingreflex opened this issue Oct 9, 2016 · 1 comment

Comments

@laggingreflex
Copy link
Contributor

laggingreflex commented Oct 9, 2016

It seems the library name has changed from node-google-translate-free to node-google-translate-skidz on npm. But this github project is still called -free. And packages with both names exist on npm, -free being the outdated one.

This might confuse users. It also creates problem for contributers, when you clone this repo from github it clones as -free and npm link links it with that name which the project using it isn't able to find.

Please unpublish the -free package from npm (you might need to email them to remove it entirely or have it redirected) and rename this github repo to -skidz (github handles redirects automatically I think)

@statickidz
Copy link
Owner

Hi, library its different on NPM because someone uploads node-google-translate-free to npm first with this code. I'll change repo name to mach with NPM name. Thanks.

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