-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
npm version is outdated #257
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
Comments
This isn't even my repository and have no immediate intent on maintaining it. I have no idea how browser side stuff uses npm so I have no context on how to manage it properly. If somebody would like to step up and help with that, I'd be happy. But until then, it's unmaintained. |
Also worth noting, that is also published from a fork at https://github.com/defunctzombie/raven-js |
You can use npm packages in your client-side for a quite long time now thanks browserify and webpack There is also a way to change an npm package owner: just write to npm orgs and claim it should be official one. |
Regarding management: |
I have permission to the repository, I just don't know what to do with it. Feel free to submit a pull request along with some documentation for this process so I have information to make a judgement call. |
https://www.npmjs.org/package/raven-js
1.1.11 last updated 6 months ago
Latest tagged version here is 1.1.16
Please publish to
npm
but consider closing #256 prior publishing.The text was updated successfully, but these errors were encountered: