


vite Official default configuration, if the resource file is packaged in the assets folder, the hash value will be added to the image name, but if it is introduced directly through: src="imgSrc", it will not be parsed during packaging, causing the development environment Can be imported normally, but cannot be displayed after packaging
We see that we actually do not want the resource files to be compiled by wbpackIt will be easier to put the images in the public directory, whether it is a development environment or production environment, you can always keep the image path consistent with the root directory, this is consistent with webpack
See this, maybe the problem is solved, if in Vite does need to put static files in assets. Let’s look down:
Here we first assume:
Static file directory: src/assets/images/
Our target static file is in src/assets/images/home/home_icon.png
<img src="/static/imghwm/default1.png" data-src="require('@/assets/images/home/home_icon.png')" class="lazy" : / alt="vue3+vite assets dynamically introduce images and solve the problem of incorrect image path not being displayed after packaging" >
We tried require dynamic introduction and found an error: require is not defind
, this is because require is a method belonging to Webpack
The first way (suitable for processing single linked resource files)
import homeIcon from '@/assets/images/home/home_icon.png' <img src="/static/imghwm/default1.png" data-src="homeIcon" class="lazy" : / alt="vue3+vite assets dynamically introduce images and solve the problem of incorrect image path not being displayed after packaging" >
The second way Method (suitable for processing multiple linked resource files)
Recommended, the variables passed in this way can be dynamically passed in the file path! !
Static resource processing | Vite official Chinese document
new URL() import.meta.url
Here we assume:
Tool file Directory: src/util/pub-use.ts
pub-use.ts
// 获取assets静态资源 export default const getAssetsFile = (url: string) => { return new URL(`../assets/images/${url}`, import.meta.url).href }
Use
import usePub from '@/util/public-use' setup () { const Pub = usePub() const getAssetsFile = Pub.getAssetsFile return { getAssetsFile } }
to include the file path
<img src="/static/imghwm/default1.png" data-src="getAssetsFile('/home/home_icon.png')" class="lazy" : / alt="vue3+vite assets dynamically introduce images and solve the problem of incorrect image path not being displayed after packaging" >
The third method (applicable to processing multiple linked resource files)
is not recommended. The files introduced in this way must be specified to the specific folder path, and the incoming variables can only be The file name cannot contain the file path
Use vite's import.meta.glob
or import.meta.globEager
. The difference between the two is that the former is lazy Load resources, which are introduced directly.
Here we assume:
Tool file directory: src/util/pub-use.ts
pub-use.ts
// 获取assets静态资源 export default const getAssetsHomeFile = (url: string) => { const path = `../assets/images/home/${url}`; const modules = import.meta.globEager("../assets/images/home/*"); return modules[path].default; }
Use
import usePub from '@/util/public-use' setup () { const Pub = usePub() const getAssetsHomeFile = Pub.getAssetsHomeFile return { getAssetsHomeFile } }
Cannot include the file path
<img src="/static/imghwm/default1.png" data-src="getAssetsHomeFile('home_icon.png')" class="lazy" : / alt="vue3+vite assets dynamically introduce images and solve the problem of incorrect image path not being displayed after packaging" >
Supplement: If the background image is introduced (must use a relative path)
.imgText { background-image: url('../../assets/images/1462466500644.jpg'); }
The production environment will automatically add it hash, and the path is correct
The following incorrect usage, using the absolute path can be displayed normally in the development environment, but it will cause the packaged path to be incorrect
.imgText { background-image: url('src/assets/images/1462466500644.jpg'); }
Production environment resources 404:
The above is the detailed content of vue3+vite assets dynamically introduce images and solve the problem of incorrect image path not being displayed after packaging. For more information, please follow other related articles on the PHP Chinese website!

前端有没有现成的库,可以直接用来绘制 Flowable 流程图的?下面本篇文章就跟小伙伴们介绍一下这两个可以绘制 Flowable 流程图的前端库。

vue不是前端css框架,而是前端JavaScript框架。Vue是一套用于构建用户界面的渐进式JS框架,是基于MVVM设计模式的前端框架,且专注于View层。Vue.js的优点:1、体积小;2、基于虚拟DOM,有更高的运行效率;3、双向数据绑定,让开发者不用再去操作DOM对象,把更多的精力投入到业务逻辑上;4、生态丰富、学习成本低。

Vue3如何更好地使用qrcodejs生成二维码并添加文字描述?下面本篇文章给大家介绍一下Vue3+qrcodejs生成二维码并添加文字描述,希望对大家有所帮助。

本篇文章我们来了解 Vue2.X 响应式原理,然后我们来实现一个 vue 响应式原理(写的内容简单)实现步骤和注释写的很清晰,大家有兴趣可以耐心观看,希望对大家有所帮助!


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

WebStorm Mac version
Useful JavaScript development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

SublimeText3 Chinese version
Chinese version, very easy to use

Safe Exam Browser
Safe Exam Browser is a secure browser environment for taking online exams securely. This software turns any computer into a secure workstation. It controls access to any utility and prevents students from using unauthorized resources.

Dreamweaver Mac version
Visual web development tools
