jxnblk/mdx-deck

Working with static assets (images) in v3

Open

#401 opened on Jul 18, 2019

View on GitHub
 (9 comments) (9 reactions) (0 assignees)JavaScript (11,169 stars) (662 forks)batch import
bughelp wanted

Description

Before 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?

Contributor guide

Tech stack
javascriptreact
Domain
frontenddocumentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
mdx deckReactstatic assets handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Examine the mdx deck v3 documentation and source code to understand how static assets are served. The user reports that placing images in a 'static' folder did not work. Investigate the webpack configuration or any custom handling for assets. Check the issue comments for any suggested workarounds or official solutions. The fix likely involves updating documentation to clarify the correct method for including static images in v3.