-
-
Notifications
You must be signed in to change notification settings - Fork 735
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
Consider having installation section with at least the npm package name #208
Comments
Everything worth using lives in the npm registry, so that should be the default assumption :-) However, I thoroughly agree that the readme should be more informative here - if you'd follow the example in https://raw.githubusercontent.com/ljharb/is-typed-array/master/README.md for the version number, the npm badge, and for funsies, the dep/dev dep badges and the license image (using the same footnote style), that'd be appreciated! |
@jinalskothari please let me know if you're interested in making a PR for this. |
@ljharb, I can take it up in 3 days and make PR. I'll check and post here before starting to avoid duplicated effort. |
@jinalskothari should i take care of this? |
Sorry I couldn't find time. @ljharb Yes please. |
It may not be obvious to all that this lib lives in the npm registry with the same package name. It may be helpful to have a section in readme with this information. Happy to make a PR.
The text was updated successfully, but these errors were encountered: