10 Replies
which one?
the 404 or the source map error?
check that your favicon is in a file called
favicon.ico, if it's a .png you'll need to change it in your html <link rel="favicon" href="favicon.png">
if it's set up correctly, you should check that the file is in the correct place for your server to discover it, and that your server is able to handle images (eg in express.js you would need to configure this)/
if you dont have a favicon, you can safely ignore the error.
---
the yellow warning is harmless, sourcemaps dont really matter all that much. and judging by that uri, it's a v2 extension, meaning it's one you've downloaded rather than one you're making.ye
ok so i dont have the favicon rn but if i add a favicon would this error get away ?
but at the same time i got 2 boxicons links does that makes any sense or no
yes, if you have a file where it's being requested, then you won't get a 404 error
this is just overhead. The first one will be requested, downloaded, and parsed, and then the second one will be requested, downloaded, and parsed, overwriting any selectors from the first one. At best it slows down your page, at worst it causes strange errors because @latest and @2.1.2 aren't the same and you end up with some rules from one and some from the other
so which one should i delete
the 2.1.2
ig
I wouldn't use a
latest for a production websitewell let me make it clear for u brother
i'm creating a portfolio for my self
which i've been looking for months, and i finally i;m creating it
and all i need it
is icon of the website, and to fix these errors
and ready to put it online
but i would like a better option from u
which one to use
and should i add a preloader?
you probably shouldn't use
latest because that might change a month from now and break your site
as for the preloader, no ideamm ok thanks btw