-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
relative image path ? #37
Comments
I'd really like to have support for this, but don't have time to implement it right now. Would you be interested in doing this as a PR? |
Same time situation for me, but I would love too... Let's see. |
As a workaround, I am using the imageFactory = ({ src, ...props }) => {
const imgSrc = src.startsWith('http')
? src
: <construct-absolute-url>
return <img {...props} src={imgSrc} />;
};
// ...
<Document components={{ img: this.imageFactory }} |
helfi92
added a commit
to helfi92/taskcluster
that referenced
this issue
Feb 22, 2019
This is because webpack was not picking up src images properly. This should be no longer the case once frontarm/mdx-util#37 is fixed.
helfi92
added a commit
to helfi92/taskcluster
that referenced
this issue
Feb 22, 2019
This is because webpack was not picking up src images properly. This should be no longer the case once frontarm/mdx-util#37 is fixed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sorry I was not able to handle by myself...
Have a markdown containing an image tag:
I was assuming, the mdx-loader would resolve the picture from the markdown document file, and then let webpack do the regular job (take the picture, move it to the static dist, hash...) .
But it looks it's not the case... Is it something I can achieve (I mean with regular markdown, without
import './img.jpg')
Have you any thoughts ? Thanks
The text was updated successfully, but these errors were encountered: