This repository has been archived by the owner on Oct 5, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 123
Publish to npm #56
Comments
I don't really have a workflow that facilitates publishing in multiple places just yet (ie, grunt-bump or gulp-bump), so this is probably not going to happen anytime soon. |
+1 (I'm sure you've already seen this but you have a good workflow example there: http://ponyfoo.com/articles/my-first-gulp-adventure) |
I've got a good workflow I'd put in place if I did (see this), I just don't have time to work on this. |
+1 |
+1 ^ 3 :-) |
+1 |
@seiyria Can we do anything to help? |
It's really just a matter of me making a workflow to help out, but this hasn't really been a priority. You can still install via npm with |
Fair enough - if you come up with some tasks to help automating the release workflow - let us know ;) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As the title says.
The text was updated successfully, but these errors were encountered: