-
Notifications
You must be signed in to change notification settings - Fork 232
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
Update npm version #250
Comments
I don't have access to push to NPM atm. @lynndylanhurley will have to bump + push. |
[EDIT]: I forgot, @dyaa was the one that created the package. We will need him to give us access. |
@dyaa - I apologize for my previous comment. I'm an idiot. |
any update on this? We're referencing the git repo directly and it's getting pretty hard to manage. Thanks! |
I've been unable to contact @dyaa. I just sent him an email, and I cc'd the npm dispute resolution team. So hopefully the problem will be resolved soon. Sorry, this is a weird situation. |
@lynndylanhurley Can you check your email ... |
Got it, thanks @dyaa!! I’ll try to publish ASAP!
|
thanks @dyaa! |
Thanks! |
please close this if resolved |
Pushed v0.0.29 to NPM yesterday! |
The version on npm is a year old,
0.0.24-beta1
. Could we get then newest version up on npm for those of use using webpack and similar?The text was updated successfully, but these errors were encountered: