Let's say you have a simple component in NuxtJS and VueJS, a static image for a blog post.
<template>
<article class="post__image">
<img class="image" src="~/assets/images/imageName.jpg" alt="post picture">
</article>
</template>
Simple enough, right? But you don't want to have the same image for every blog post, so maybe you're trying to add it dynamically, getting the image name through a prop and using Vue's v-bind directive, like so:
<template>
<article class="post__image">
<img class="image" :src="`~/assets/images/${imageName}.jpg`" :alt="`${imageName} picture`">
</article>
</template>
<script>
export default {
name: 'PostImage',
props: {
imageName: String
},
}
</script>
And then you notice that that doesn't work. But why? The vue syntax is correct, so what's the problem? Well, there's something else at play here.
Behind the scenes, webpack replaces the image path with a module request at build time. That's fine for static images, because their paths are known at build time, but for dynamic images it's a different story, as webpack can't know what their paths will evaluate to at run time, so that won't work.
The solution is to make a module request for the images, so that webpack can work its magic on them before loading them on the page. That's done by using require(...), with the correct image path.
So your images will have to be loaded like this:
<img
class="image"
:src="require(`~/assets/images/${this.imageName}.jpg`)"
:alt="`${imageName} picture`"
>
You could also clean that up a bit, and extract the require part into a computed property, for better readability:
<template>
<article class="post__image">
<img class="image" :src="imageSource" :alt="`${imageName} picture`">
</article>
</template>
<script>
export default {
name: 'PostWithImage',
props: {
imageName: String
},
computed: {
imageSource() {
return require(`~/assets/images/${this.imageName}.jpg`)
},
}
}
</script>