You will notice in the project structure we have two directories for assets:
/src/assets/. What is the difference between them? Some are static assets while the others are processed and embedded by the build system.
So let’s try to answer the question above. We’ll first talk about using regular assets then we’ll see what the difference is for static assets.
Regular assets - /src/assets
*.vue components, all your templates and CSS are parsed by
css-loader to look for asset URLs. For example, in
<img src="./logo.png"> and
"./logo.png" is a relative asset path and will be resolved by Vite as a module dependency.
Since these assets may be inlined/copied/renamed during build, they are essentially part of your source code. This is why it is recommended to place Vite-processed assets inside
/src/assets, along side other source files. In fact, you don’t even have to put them all in
/src/assets: you can organize them based on the module/component using them. For example, you can put each component in its own directory, with its static assets right next to it.
Asset Resolving Rules
Relative URLs, e.g.
./assets/logo.png will be interpreted as a module dependency. They will be replaced with an auto-generated URL based on your Vite output configuration.
URLs prefixed with
~ are treated as a module request, similar to
import 'some-module/image.png'. You need to use this prefix if you want to leverage Vite’s module resolving configurations. Quasar provides the
assets alias out of the box, so it is recommended that you use it like this:
<img src="~assets/logo.png">. Notice
~ in front of ‘assets’.
Static Assets - /public
Root-relative URLs (e.g.
/logo.png – where ‘/’ is your publicPath) or
logo.png are not processed at all. This should be placed in
public/. These won’t be processed at all. The content of the public folder is simply copied over to the distributable folder as-is.
Assets vs Statics
Files in the “assets” folder are only included in your build if they have a literal reference in one of your Vue files. Every file and folder from the “public” folder are copied into your production build as-is, no matter what.
When not building a SPA/PWA/SSR, then
/public/favicon.ico will NOT be embedded into your app because they would not serve any purpose. For example, Electron or Cordova apps do not require those files.
More info with Vite
Please read Vite’s guide here.