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
I was wondering if you're open to publishing tags (and maybe releases) on this repo?
This will allow installing a specific version using npm, even if you don't list the package on npmjs.com.
As I mentioned in the linked issue, I don't use npm to install, or bring in dependencies. If you would like to add it if it makes using the plugin better for you, go for it. Just be mindful that I'd more than likely not update those changes as time goes, but I'm all for someone doing that if it helps.
I understand. I think I could submit a PR with a github action that can automate the release. With that in mind, I was wondering if you make a habit of updating the version in the package.json when you merge a PR?
Hi,
Thanks for a great utility!
I was wondering if you're open to publishing tags (and maybe releases) on this repo?
This will allow installing a specific version using npm, even if you don't list the package on npmjs.com.
e.g.
Relates to #74
The text was updated successfully, but these errors were encountered: