Working with static assets (images) in v3
See original GitHub issueBefore I used my images as:
![](images/something.png)
<img src="images/something.png" />
While keeping a top level images
folder in my project and that worked fine. With the move to v3 this stopped working. I dug a bit into Gatsby and tried moving my images folder into a static
folder, but that did not work.
How can we use static resources, such as images? Is there still a folder being served?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:9
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Static Asset Handling - Vite
Common image, media, and font filetypes are detected as assets automatically. You can extend the internal list using the assetsInclude option.
Read more >Using static module assets | Apostrophe 3 Documentation
While developers can place static files in the top-level /public folder of the project, which allows a file like /public/images/bg.png to be ...
Read more >Using Static Asset Files in Angular | mobiarch
Similar smart features exist for other static asset files like images. In today's article I will explore this area.
Read more >Static Files & Images | Django Framework (3.0) Crash Course ...
Static Files & Images | Django Framework ( 3.0 ) Crash Course Tutorials (pt 4).
Read more >How to manage static files (e.g. images, JavaScript, CSS)
Websites generally need to serve additional files such as images, JavaScript, or CSS. In Django, we refer to these files as “static files”....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Can confirm that the import way works but requires a reload of the dev server every time you add an image 😞
I published a minimal reproduction repo: https://github.com/HoverBaum/bug-mdx-deck-401
The webpack workaround appears to have the drawback that I have to restart the dev server every time I add an image. That’s unacceptable; any way to make this dynamic?