gatsby-plugin-favicon
gatsby-plugin-favicon copied to clipboard
Creatiwity
UNMAINTAINED - Favicon Gatsby plugin
The package wouldn't install on projects with react 17 ``` npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: [email protected] npm...
https://www.gatsbyjs.com/plugins/gatsby-plugin-favicon/ only shows the words 'README.md' 
I updated my project to Gatsby 3 and can’t start the dev server unless I disable gatsby-plugin-favicon. I am on Windows with WSL 2, this is the error that comes...
Hi! In your `favicon` dependency, NPM audit shows that the dependency `to-ico` is vulnerable to CVE-2020-7661, which is rated as a high severity vulnerability. I've raised this issue with that...
Is there a dependency upgrade on the horizon? The `npm audit` steps listed don't resolve this... ```# Run npm update null --depth 2 to resolve 1 vulnerability ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ Low...
Alright, I have overseen this part in the readme :D It seems like you mention it, but why is it required to set this meta tag? Wouldn't it be better...
Error: The specified procedure could not be found. \\?\C:\projects\runleeds\Run-Leeds-Gatsby\node_modules\favicons\node_modules\sharp\build\Release\sharp.node It seems that the favicon libary used by https://github.com/Creatiwity/favicons-webpack-plugin is out of date? May not be the issue... The build is...
It should be made noticed in the README that this plugin is incompatible with https://www.gatsbyjs.org/packages/gatsby-plugin-manifest/ as it overrides its values, which is an official plugin and comes activated by default...
Webpack is a peer dependency of `favicons-webpack-plugin`, so it needs to be a peer dependency of `gatsby-plugin-favicon` as well 🙂
Thank you for the excellent plugin! I'd love to be able to provide a few different favicon sources for different sizes—what works at 16x16 isn't appropriate for 148x148, and vice-versa....
