Nicolas B.

Results 6 comments of Nicolas B.

For consistency with the package markdown remark, I think it should work with relative path: https://www.gatsbyjs.org/docs/working-with-images-in-markdown/#configuring-for-images-and-posts-in-different-directories Your absolute paths would be declared in `gatsby-config.js`in `gatsby-source-filesystem`, and then use relative path...

For the crash with sharp, i found this workaround: https://florian.ec/blog/gatsby-build-netlify-segmentation-fault so you can tag this issue as an enhancement

In addition to the workaround listed above, this pull request #18 allows you to manage a large volume of images.

> @korukugashi how did you finally solve this? > > I have a data base with local of images (relative routes, images on the filesystem) and I don't know what...

So you can't use gatsby-image, isn't it?