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
First and foremost, i understand the daily load of work of everybody and especially this is open source so I'm not here to discuss governance. I'd just like to know if this project is still opened to contributions such as patches and features and if we can hope PRs to be merged in a reasonable timeframe.
Respectfully,
Reacted by Patt O'Brien
Reacted by t-animal, Alessandro Bellesia and Patt O'Brien
Hi @y-nk , thanks for your understanding. My daily job is indeed extremely busy in the past years. but this little package are used and running fine in my own project. If you found any issues with it please feel free to create an issue or open a PR directly. Sorry that I didn't pay much attention to github in general since I switch to use gitlab in my work. My apologizes.
@axe-me Thank you for your answer. I understand your PoV, everyone's busy indeed :)
the core of this message was because the tickets i've opened in the past were left with no answer. While i do understand that you have no time at all, I was worried that if I invested time in forking/fixing them myself, it'd be wasted because not merged! This happens a lot and I don't want ending up with a fork to maintain + publish and a "fork war" (where forks take over upstreams etc etc) (so far I have fixes in the forms of pnpm patches running locally)
if you are opened to PRs, i'll submit some to fix #132 and #134 probably in January due to end of year closing.
Sorry to nudge you on this, and obviously no pressure to respond !
Any chance we could get #133 merged and published ? I'd also like to submit patches for a couple of issues above, do you think you'd have the bandwidth to have a look ?
Activity
axe-me commentedon Dec 11, 2025
Hi @y-nk , thanks for your understanding. My daily job is indeed extremely busy in the past years. but this little package are used and running fine in my own project. If you found any issues with it please feel free to create an issue or open a PR directly. Sorry that I didn't pay much attention to github in general since I switch to use gitlab in my work. My apologizes.
y-nk commentedon Dec 11, 2025
@axe-me Thank you for your answer. I understand your PoV, everyone's busy indeed :)
the core of this message was because the tickets i've opened in the past were left with no answer. While i do understand that you have no time at all, I was worried that if I invested time in forking/fixing them myself, it'd be wasted because not merged! This happens a lot and I don't want ending up with a fork to maintain + publish and a "fork war" (where forks take over upstreams etc etc) (so far I have fixes in the forms of pnpm patches running locally)
if you are opened to PRs, i'll submit some to fix #132 and #134 probably in January due to end of year closing.
axe-me commentedon Dec 11, 2025
I will definitely find some time to resolve these issues. However, I cant guarantee a time frame. maybe during xmas break.
jbsouvestre commentedon Feb 18, 2026
Hi @axe-me ,
Sorry to nudge you on this, and obviously no pressure to respond !
Any chance we could get #133 merged and published ? I'd also like to submit patches for a couple of issues above, do you think you'd have the bandwidth to have a look ?
Thanks a lot for you work on this project