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
Nobody (including myself!) has done a lot of work here in the last year or so, but a couple recent issues, brought my attention back to this repo. When I first got added on as a maintainer, I made a laundry list of to-do issues, and never got half of them done. I’m currently dedicating some time this week and next week to try and get through them:
Hopefully I’ll get a release out the door with all of those updates (and a few other assorted bits) before the end of the month.
There are some other, older issues that I’m not actively planning to work on. If you have a strong need for something not listed above, please comment and let me know! (PRs are always welcome, too.)
A few of these issues involve either breaking changes or require fairly complex code to support them (e.g. promises vs. callbacks). This library gets a lot of downloads on NPM, so I plan to continue deprecating-but-still-supporting the old stuff. However, that stuff eventually needs to be cleaned out, so I’m planning to fully remove most deprecated functionality in a major, breaking change in January 2025. (Maybe we’ll cut a 1.0!)
The text was updated successfully, but these errors were encountered:
Nobody (including myself!) has done a lot of work here in the last year or so, but a couple recent issues, brought my attention back to this repo. When I first got added on as a maintainer, I made a laundry list of to-do issues, and never got half of them done. I’m currently dedicating some time this week and next week to try and get through them:
Hopefully I’ll get a release out the door with all of those updates (and a few other assorted bits) before the end of the month.
There are some other, older issues that I’m not actively planning to work on. If you have a strong need for something not listed above, please comment and let me know! (PRs are always welcome, too.)
A few of these issues involve either breaking changes or require fairly complex code to support them (e.g. promises vs. callbacks). This library gets a lot of downloads on NPM, so I plan to continue deprecating-but-still-supporting the old stuff. However, that stuff eventually needs to be cleaned out, so I’m planning to fully remove most deprecated functionality in a major, breaking change in January 2025. (Maybe we’ll cut a 1.0!)
The text was updated successfully, but these errors were encountered: