Strugling with favicon #12387
Replies: 4 comments
-
If you are using Quasar v1 with
|
Beta Was this translation helpful? Give feedback.
-
Thank you for the help. I am using Quasar 2.0 and Icongenie 2.4.0, and did execute the command on the project root folder. However, in production, I am still not getting the files. It's deployed on Vercel and I followed the documentation regarding deploying there, including creating the vercel.json I will try to figure that out, unless you have any idea why that might be the case. |
Beta Was this translation helpful? Give feedback.
-
I think it may have something to do with the quasar meta plugin, which I am using. |
Beta Was this translation helpful? Give feedback.
-
I'm experiencing a similar issue, generated with icongenie, everything works fine during quasar dev, but when I build and try to run with quasar serve, I'm getting 404s all around, like: GET --My setup: node18.20.4 Even scaffolding a new project produced the same issue. I have a feeling it's something trivial but I'm at a loss here. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I have used the Icongenie CLI and it successfully created the icons and copied them to statics/icons.
I then copied the tags it gave me and put them on the html head.
I can see the files exist and are valid images.
However, i keep getting 404s on the browser.
The documentation says these types of assets should be in the /public folder, however there is only /statics and that is where Icongenie puts them. Any tips on what could be happening?
Beta Was this translation helpful? Give feedback.
All reactions