| Name |
Last commit
|
Last update |
|---|---|---|
| bin | ||
| lib | ||
| media | ||
| scripts | ||
| src | ||
| test | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .jshintignore | ||
| .jshintrc | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| TROUBLESHOOTING.md | ||
| appveyor.yml | ||
| binding.gyp | ||
| package.json |
Maintainers get a lot of emails about errors from users whom we inevitably have to direct to the issue tracker. I suspect this is because, when an error happens, users are encouraged to run either `npm bugs` or `npm owner ls`. `npm bugs` would fail without a bugs url, so they'll move onto `npm owner ls` and subsequently email us. By adding the `bugs` url to the package.json, _hopefully_ this will mitigate some of the emails the maintainers receive.
| Name |
Last commit
|
Last update |
|---|---|---|
| bin | Loading commit data... | |
| lib | Loading commit data... | |
| media | Loading commit data... | |
| scripts | Loading commit data... | |
| src | Loading commit data... | |
| test | Loading commit data... | |
| .editorconfig | Loading commit data... | |
| .gitattributes | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .gitmodules | Loading commit data... | |
| .jshintignore | Loading commit data... | |
| .jshintrc | Loading commit data... | |
| .travis.yml | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| LICENSE | Loading commit data... | |
| README.md | Loading commit data... | |
| TROUBLESHOOTING.md | Loading commit data... | |
| appveyor.yml | Loading commit data... | |
| binding.gyp | Loading commit data... | |
| package.json | Loading commit data... |