-
Notifications
You must be signed in to change notification settings - Fork 198
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
New release..? #124
Comments
Hi, that PR has been live in the latest release since June, it's also on npm. Let me know if there's anything more you need. Closing for now. |
Ah, it seems you're right; not sure what happened on my end, but I just removed and re-installed your package and now it seems to work just fine. Thanks much. |
Cool !
…On Thu, Jan 12, 2023, 19:54 Max Loeb ***@***.***> wrote:
Ah, it seems you're right; not sure what happened on my end, but I just
removed and re-installed your package and now it seems to work just fine.
Thanks much.
—
Reply to this email directly, view it on GitHub
<#124 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADDFBQUQKTISVDK7E3UYADWSBHOZANCNFSM6AAAAAATUO4LXA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey there, I understand that this repo isn't maintained anymore, but is there any way I can trouble you to bump a new release so that we can get #122? Much appreciated, and thanks for a great library.
The text was updated successfully, but these errors were encountered: