gatsby-plugin-manifest - Input file contains unsupported image format
See original GitHub issueStarted facing this issue recently on the Nelify build. gatsby build
works perfectly fine in the local env.
gatsby-config.js
{
resolve: `gatsby-plugin-manifest`,
options: {
name: `name`,
short_name: `sname`,
description: `desc`,
lang: `en`,
start_url: `/`,
background_color: `#fff`,
theme_color: `#a50f20`,
display: `standalone`,
icon: `static/assets/images/icon.png`,
icon_options: { purpose: `maskable` },
},
},
Nelify Deploy Logs
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Error "gatsby-plugin-manifest" Input file contains unsupported ...
I'm getting an unsupported image error when trying to deploy my Gatsby site to Netlify. The error is from the gatsby-plugin-manifest, see screenshot...
Read more >Gatsby build always throwing Input file is missing or of an ...
I am using gatsby-plugin-manifest and the image path I have put there is src/img/ninja.png, but it should have been src/images/ninja.png .
Read more >Input file contains unsupported image format - Gatsby
I'm testing a website with thousands of images and the tracedSVG query is working fine… the error implies that gatsby-plugin-sharp cannot ...
Read more >gatsby-plugin-manifest
of one of the following formats: JPEG, PNG, WebP, TIFF, GIF or SVG. Automatic mode configuration. Add the following line to the plugin...
Read more >Input file contains unsupported image format, gatsby - Qiita
【Gatsby.js】対処しよう、「Error: Input file contains unsupported image ... gatsby-starter-blog@0.1.0 ~ ├─┬ gatsby-plugin-manifest@2.6.1 ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For anyone using Netlify and facing this issue, you can add the environment variable
SHARP_IGNORE_GLOBAL_LIBVIPS
with valuetrue
to https://app.netlify.com/sites/<your site>/settings/deploys#environmentThis fixed the issue for me.
This sounds like is a duplicate of #20698
Likely happening because Netlify has global
libvips
installed that is incompatible with a local sharp version. The suggested solution is to re-install dependencies from scratch usingSHARP_IGNORE_GLOBAL_LIBVIPS=true
:We’re marking this issue as answered and closing it for now but please feel free to comment and mention me if you would like to continue this discussion. We hope we managed to help and thank you for using Gatsby! 💜