-
Notifications
You must be signed in to change notification settings - Fork 43
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
publish new version on npm #20
Comments
You can install from GitHub in the meantime |
the only reason for asking about that is exactly to avoid this ;-) maybe we could rely on a specific tag. but I'd need to clarify that. we definitely prefer to rely on a published release |
Sounds good, i'll do that today |
done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey @dcposch,
we recently got #19 merged by @nazar-pc (thanks for that! :-)). Can you publish a new release to NPM that includes this change? Otherwise we need to publish this separately and we'd like to avoid that.
Best regards,
Marco
The text was updated successfully, but these errors were encountered: