Start a new pull request in StackBlitz Codeflow.

• github-mrq86l-s2dqph (Open reproduction)

Changing to url('~/public/favicon.ico') does the trick.

And shouldn't it be this way to refer to local assets/public file?

Changing to url('~/public/favicon.ico') does the trick.

No it doesn't really do the trick. Because this results in the static file being copied as an asset.

Which means that:

• it doesn't benefit from proper browser caching afterwards, because of the name hashing
• gets needlessly preloaded as if it was a critical part of the application (it's a referenced asset, technically, after all)

We're having this issue with our font faces, ie this (if we add the ~/public prefix to "fix" the warning):

@font-face {
  font-display: swap;
  font-family: "Poppins";
  font-style: normal;
  font-weight: 100;
  src:
    url("/fonts/poppins/poppins-v19-100.woff2") format("woff2"),
    url("/fonts/poppins/poppins-v19-100.woff") format("woff");
}

@font-face {
  font-display: swap;
  font-family: "Poppins";
  font-style: normal;
  font-weight: 300;
  src:
    url("/fonts/poppins/poppins-v19-300.woff2") format("woff2"),
    url("/fonts/poppins/poppins-v19-300.woff") format("woff");
}

[...]

This will then end up inside the manifest and all other places where we then have to specifically remove it from. And we still lose caching.

I'm also seeing those warnings on all my Nuxt projects where I'm referencing files in my styles.
3.11.0's release notes did mention a "reimplementation of Vite's public asset handling" with #26163

[...] this PR takes full control over public assets and bypasses the vite pipeline entirely for them.

With vite.publicDir.$resolve(val) now only returning false.

I am also getting this warning at build time with:

.landing-grid {
  background: url(/topo_landing_bg.svg);
}

in 3.11.0/1 leads to

/topo_landing_bg.svg referenced in ... didn't resolve at build time, it will remain unchanged to be resolved at runtime

Same issue here, I'm using Nuxt version 3.11.2. The issue persists for the npm run build and npm run generate.

Same issue. Since I have a lot of public files, too many warnings are generated during build.

Same for me with version 3.11.1