You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm recently struggling to use this library.
When I search about nyc in Google, of course it reach something related to New york city. That is not problem.
However, even I searched in "nyc code coverage" or "nyc node", most of pages are the pages related to Hackathon or conferences.
Download count of this library is currently growing, so I guess many people will struggle with this problem when many people use this library. Therefore, I suggest to define something alias for nyc.
For example, if you name code name for nyc versions like Android versions, users will write articles with these name, and articles related to nyc will be easier to be found in Google.
The text was updated successfully, but these errors were encountered:
I found the easiest way to learn more about a particular package is to use http://npm.im/{PACKAGE_NAME}, which redirects to the npm page for that package. That page usually has a README and links to issue trackers etc.
I'm recently struggling to use this library.
When I search about nyc in Google, of course it reach something related to New york city. That is not problem.
However, even I searched in "nyc code coverage" or "nyc node", most of pages are the pages related to Hackathon or conferences.
Download count of this library is currently growing, so I guess many people will struggle with this problem when many people use this library. Therefore, I suggest to define something alias for nyc.
For example, if you name code name for nyc versions like Android versions, users will write articles with these name, and articles related to nyc will be easier to be found in Google.
The text was updated successfully, but these errors were encountered: