Since there's been a lot of important commits (for the ecosystem, such as promises) since the last release in January, perhaps it's time to tag a new release?
Yet there are some things to finish not completed.
Is there a checklist somewhere?
I looked at an example with promises and it turns out the latest release still has callbacks, so I'd be interested in helping with getting the new version shipped.
@GreLI please share with us what you have, there hasn't been any progress for a very long time.
You can commit work in progress to a new branch, so we can view and try to help.
This is the meaning of "open" in open source (:
Well, at most I was busy making svgo *.svg possible. It's done, I just want to tweak and cleanup the plugins, fix some dumb things and release version 1.0. That will allow a faster release pace.
Any idea of a timeline on when the release is expected? Will it be in 2017? Need dat recursive folder feature HNNNNGGGG. Awesome work by the way!
@GreLI we all appreciate your work. I think it might be time to put new features on shelf and make sure we avoid breaking for the community that is dependent on things like promises, then keep working on those said features.
Need dat recursive folder feature HNNNNGGGG. Awesome work by the way!
Unfortunately it has been lost in that commit. :disappointed: It's hard to make it properly in a async way.
@GreLI: Yes, a new release to npm would be great!
I have sometimes strange issues with other modules using svgo (imagemin-svgo).
Same here, gulp-svgmin has some issues and we need inlineStyles :)
svgo version 1.0.0 comes with a Promise based API,
you have to update some plugins/adapters for svgo.
Yay! Thanks a lot for the release, great work :)
I believe this can be closed now.
Yeah, thanks for reminder.
Most helpful comment
Well, at most I was busy making
svgo *.svgpossible. It's done, I just want to tweak and cleanup the plugins, fix some dumb things and release version 1.0. That will allow a faster release pace.