Updated package.json to include keywords #4

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
3 participants
@twigz20

twigz20 commented Jan 24, 2017

I noticed that you were missing some keywords in your package.json file, so I've added them. Let me know if there are other/different keywords that you would use instead.

@coveralls

This comment has been minimized.

Show comment
Hide comment
@coveralls

coveralls Jan 24, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling b9bd469 on twigz20:master into 5ea6398 on bootprint:master.

Coverage Status

Coverage remained the same at 100.0% when pulling b9bd469 on twigz20:master into 5ea6398 on bootprint:master.

@coveralls

This comment has been minimized.

Show comment
Hide comment
@coveralls

coveralls Jan 24, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling b9bd469 on twigz20:master into 5ea6398 on bootprint:master.

coveralls commented Jan 24, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling b9bd469 on twigz20:master into 5ea6398 on bootprint:master.

@nknapp

This comment has been minimized.

Show comment
Hide comment
@nknapp

nknapp Jan 24, 2017

Member

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.

Member

nknapp commented Jan 24, 2017

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.

@nknapp nknapp closed this Jan 24, 2017

@twigz20

This comment has been minimized.

Show comment
Hide comment
@twigz20

twigz20 Jan 24, 2017

Thanks for taking the time to explain this in detail for me. I appreciate it. Lesson learned for next time.

twigz20 commented Jan 24, 2017

Thanks for taking the time to explain this in detail for me. I appreciate it. Lesson learned for next time.

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