-
Notifications
You must be signed in to change notification settings - Fork 110
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
Cool kids update their OSS dependencies #339
Comments
Congratulations @untra , you're now a maintainer. |
@untra @JoshuaWalsh give me your npm usernames and I will give you write access to the npm package also. |
@jariz my npm username is also |
@jariz I think #327 is a prerequisite for being able to review dependency PRs quickly:
If you have a chance, it'd be great if you can review the PR. Thanks |
There are a number of rotting dependencies in this package, with PRs already opened by automation bots to address.
this package is becoming problematic because it relies on a number of dead and rotting npm packages.
You dont have to release updates every time, but at least once a year would be a significant improvement.
Please update these dependencies and cut a new release of the npm package: I have half a mind to fork this project and make a custom release with updated deps.
Happy to assist with this @jariz however possible.
The text was updated successfully, but these errors were encountered: