-
Notifications
You must be signed in to change notification settings - Fork 26
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
The readme on npm is 0.4.0 #12
Comments
Yeah... I forgot to update it until after the release. It seemed to me like it would be overkill to do another release just for up-to-date docs on the npm site? |
I guess I'll close this whenever there's a new release :) |
I agree that might be a bit overkill, but the links are to 0.4.0 so lazy copy-pasters like me will run around with an older version :p |
Fair enough.. I'll try to come up with an excuse to release again soon :) |
I'm using this for a project and I have found a bunch of bugs ^-^ Will make issues of them soon, so they might make for good candidates for a new release :) |
@TheGrandmother please do open issues for any bugs you find! It's much appreciated. :) My worst nightmare is that people find bugs in my code and don't report them lol |
Haha I know the feeling ^^ I'll make the issues later this afternoon :) |
Depending on the bug it might be a problem with an underlying dependency (the only "decoding" we do directly here is overlaying progressive gif frames) but if you find something, report it here and we'll sort out the root cause. Thanks again! |
The readme on npm is still for version
0.4.0
:pThanks for a dank library otherwise!
The text was updated successfully, but these errors were encountered: