While working on @vitejs/plugin-legacy I noticed some incorrect definitions in index.html.
I guess we didn't notice this because the (fallback) favicon.ico gets rendered in the browser.
I also wrote an e2e test, to verify if all favicons with correct paths get rendered in the browser to prevent an issue like this from happening in the future.
While working on
@vitejs/plugin-legacyI noticed some incorrect definitions inindex.html.I guess we didn't notice this because the (fallback) favicon.ico gets rendered in the browser.
I also wrote an e2e test, to verify if all favicons with correct paths get rendered in the browser to prevent an issue like this from happening in the future.