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
Doing an npm install after cloning this project downloads 1658 dependencies, there are also many warnings about deprecated and vulnerable packages. Maybe it's a good idea to update, remove, or switch some dependencies to actively maintained projects.
Holy moly, I had never looked at the package.json of this plugin before and was just using it blindly. This is an insane tree of dependencies for a plugin to another library. I can't imagine this initiative would get blocked either. I'd be willing to contribute time towards this initiative on my spare time. Can happily help with linting related dependencies!
EDIT: I can probably take on updating testing related dependencies too. Will try to get a PR up for both by this weekend.
Doing an npm install after cloning this project downloads 1658 dependencies, there are also many warnings about deprecated and vulnerable packages. Maybe it's a good idea to update, remove, or switch some dependencies to actively maintained projects.
Is this a direction worth pursuing?
The text was updated successfully, but these errors were encountered: