maintainer?
chrisdrackett opened this issue · 12 comments
@malte-wessel curious what your plans for this package are. I see in the last couple days there has been some activity resulting in pull requests. However, I also see that the project hasn't been updated in quite a while.
I'm also thinking about starting to use the project, but based on the current state think I'll probably be making my own fork so I can pull in fixes from others as well as make my own. Hopefully there is a way to get all these fixes from the community into a canonical repository.
hey @chrisdrackett I'm currently too busy to take care of this project. I would appreciate If anyone could take over.
@malte-wessel I would be happy to maintain this project. If you're interested, please let me know what the steps for that look like
@tbroadley / @malte-wessel I'd also be happy to help out (not sure if I want to be the only maintainer). I may or may not think of the API/base features in a completely different way, which is worth taking into consideration :)
@malte-wessel Any thoughts about this?
I'm open for PRs, but I don't want to change the existing API (for now). Because people are already using the lib
@malte-wessel That's reasonable. Major API changes could be released as a new major version, which would allow people to stick with the current API if they wanted to.
Would you be able to at least take a look at #9 and #10? Those two PRs fix bugs that are causing console errors.
Much appreciated @malte-wessel :) Any chance you could publish a new version to NPM with these fixes?
I'm on it :)
published!
Thank you so much!
@malte-wessel great. Finally the much needed prs are merged. I will now update my projects package.json as well.
In addition to malte-wessel, I am also available to merge features in, so feel more motivated creating them! :-)