BUG: gatsby-plugin-sharp does not respect forced format depending on input format

[polarathene]

Description

I've discovered a bug which appears to be due to the sharp package, raised an issue there, this is more of a tracker to make sure gatsby-plugin-sharp gets the update when fixed(I think "sharp": "^0.21.0" in the package json will ensure any fixes are made available, eg 0.21.02?) .

If you input a JPEG image and use toFormat: PNG in graphql, it will be ignored as the chaining approach presently has a bug where the input formats mimetype will override any prior formats in the pipeline chain, even if they have force: true in their format options set.

Steps to reproduce

Use the default starter with a jpg image instead, try force/convert to png with toFormat: PNG, notice that with fixed/fluid with gatsby-image results in png format like desired in the <picture> element, but the base64 placeholder is actually jpeg.

Expected result

The base64 should be png format.

Actual result

As the pipeline called .jpeg() after .png() and the input type is jpeg, it ignored .png()'s force: true option, resulting in a base64 in jpeg format.

Rearranging the pipeline order provides the expected result(but then breaks it another way due to actual bug).

Environment

Gatsby 2.0.78 in an Alpine Docker container.

[gatsbot]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

Thanks for being a part of the Gatsby community! 💪💜

[polarathene]

Fixed in sharp 0.21.02