resize but keep proportion about sharp-cli HOT 13 CLOSED

I was looking for something like this imagemagick command:

convert -resize 640x640> *.jpg "${pattern}-%d.jpg"

from sharp-cli.

Try using the --fit inside option - see https://sharp.pixelplumbing.com/en/stable/api-resize/#resize

from sharp-cli.

Thanks a lot, that was what I was looking for.

Is there a way to overwrite the input file, or to set a pattern for naming the out files (something like ${original_name}-resized.jpg)?

All what I saw on the README file is that sharp-cli is made for one file at a time (even if bash car use jokers to change multiple files at a time).

You can have an example of such pattern in the imagemagick command above.

And it seems that overwriting is explicitly forbidden by the cli. Here is an error of the cli when trying to overwrite an input file:

Cannot use same file for input and output

from sharp-cli.

You can use url-templates for this - for example sharp resize 800 600 --fit inside -i ./src/*.jpg -o ./dest/{name}{ext}. Batch processing is supported.

from sharp-cli.

Is there a way to use sharp and url-templates directly in a CLI?

Or is it mandatory to create a js script to use both of them in cunjunction?

from sharp-cli.

Yes, you can use this right from the CLI - see my last reply for an example.

from sharp-cli.

You mean, I juste have to install url-templates globally, then to enter the following command:

sharp resize 800 600 --fit inside -i ./src/*.jpg -o ./dest/{name}{ext}

and {name} and {ext} will be automatically defined?

It is still not possible to overwrite the source file with this solution, right?

from sharp-cli.

Everything already comes with the CLI - just try and run the command in my example above. Overwriting the source file is not supported.

from sharp-cli.

You're right, I tested it and it works perfectly, impressive! Is this feature documented somewhere?

The only thing I am missing is overwriting. What a pity... I'll have to find a workaround.

from sharp-cli.

The CLI used to be able to do that, but I removed support for it since it led to problems with large files. Large files work great with streams, but we cannot use streams when saving to the same file.

I might be able to add a --overwrite flag in the CLI, which when set would overwrite the input file. Gotcha would be that you should use this flag only for small files.

from sharp-cli.

I understand the limitation that you encountered.

But I would be very happy to see this feature back in sharp.

from sharp-cli.

I created this request in #24. Closing this.

from sharp-cli.

you could pipe output to 'sponge' and save as same file. Otherwise, input file gets destroyed before reading

from sharp-cli.