Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Updated package.json to include keywords #4
Hi there. Thanks for your PR, but I don't fully understand the goal you would like to achieve.
Aren't keywords mostly terms that are not part of the name and the description that are still relevant for a package. I think, the main goal is, that if someone enters a search term which would normally not find the package (or just with a low score), but the term is a meaningful description of what the package stands for, then it should be a keyword. So that the search-engine can find it.
I'm not sure if it makes sense to include these keywords. "customize", "write" and "files" are already part of the name. "post-processor" may be reasonable, but if I search for "post-processor" in npm-search, would I expect to find something with the functionality of this package? And "ghooks" is just a dev-dependency and it does not have anything to do with the goal of the project.
Please comment if you think otherwise and I will reopen.