Adds optional 'quality' param to allow lossy jpeg output #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depending on formatting of the original image, slight lossy optimization can provide huge file-size savings over strictly lossless JPEG compression. This update adds an optional 'quality' param that can be sent along with the source image path.
Optimizer will default to lossless compression if no quality param is specified, this change will not break existing implementations of the optimizer. Updates jpegoptim command line calls to force Progressive JPG output, as they provide a better end-user experience when loading over a slow connection. PNG optimization untouched; PNGs will ignore the quality param. Readme updated to reflect new options and defaults.