Update FAQ to include section about inline asset URLs (#898)

* Update faq.md Update FAQ to include a section about inline asset URLs, as discussed in the following issue: #863 * Update faq.md Fix some text not showing * Update faq.md Add an example to the inline assets section * Update faq.md Fix spacing between beginnings of parenthesis * docs(faq): update entry about relative asset urls --------- Co-authored-by: dominikg <[email protected]>
sveltejs · Jul 9, 2024 · 0d093f2 · 0d093f2
1 parent 76a94d4
commit 0d093f2
Showing 1 changed file with 14 additions and 0 deletions.
diff --git a/docs/faq.md b/docs/faq.md
@@ -237,3 +237,17 @@ See the faq about [vite and prebundling](#what-is-going-on-with-vite-and-pre-bun
 > [svelte-package](https://kit.svelte.dev/docs/packaging) which already supports it.
 >
 > For backwards compatibility, you can keep the `svelte` field in addition to the `exports` condition. But make sure that both always resolve to the same files.
+
+### How can I use relative paths for asset references in svelte components like `<img src="./asset.png">`
+
+This is not supported out of the box. To resolve assets, you have to either import them like this:
+
+```html
+<script>
+  import assetUrl from './asset.png';
+</script>
+<img src="{assetUrl}" />
+```
+
+or use a separate tool to add this functionality.
+The 2 recommended solutions are [sveltejs/enhanced-img](https://kit.svelte.dev/docs/images#sveltejs-enhanced-img) (only for image elements) and [svelte-preprocess-import-assets](https://www.npmjs.com/package/svelte-preprocess-import-assets) (for all asset URLs).