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 off, thank you for maintaining this package—it’s been super helpful! 🙌
I was wondering if it would be possible to add Git tags for the published versions of the package? It would make it much easier to track changes and match the versions with the code.
The reason I’m asking is that I’m trying to investigate a bug reported in issue #125. To track it down, I thought I’d compare the changes between the last working version and the non-working version. However, I noticed that version 0.0.46 seems to be missing in the repository. The tags jump from 0.0.45 (commit c552916) to 0.0.47 (commit d9d7edc), even though 0.0.46 is listed on npm (link to versions on npm).
It’d be great to have that version reflected in the codebase too. Thanks so much for your time and all your work on this project! 😊
The text was updated successfully, but these errors were encountered:
Hi there!
First off, thank you for maintaining this package—it’s been super helpful! 🙌
I was wondering if it would be possible to add Git tags for the published versions of the package? It would make it much easier to track changes and match the versions with the code.
The reason I’m asking is that I’m trying to investigate a bug reported in issue #125. To track it down, I thought I’d compare the changes between the last working version and the non-working version. However, I noticed that version
0.0.46
seems to be missing in the repository. The tags jump from0.0.45
(commit c552916) to0.0.47
(commit d9d7edc), even though0.0.46
is listed on npm (link to versions on npm).It’d be great to have that version reflected in the codebase too. Thanks so much for your time and all your work on this project! 😊
The text was updated successfully, but these errors were encountered: