-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Issues with gatsby-source-filesystem #1711
Comments
The plugin can silently jsut tall if there are no files found. Make sure there are actually files at that path? (and maybe drop the trailing slash for fun) |
Think I may have sussed it. Need to be |
We should validate that the specified path actually exists… You want to work on that @MojoJojo86? |
@KyleAMathews Yeah if I can figure out how to, I'd love to have a go at it! 👍 |
I think I'm having this same issue. We've decided to update the KeystoneJS Docs site we're working on to the latest version, but when I run I checked that the folders being passed into Repro: https://github.com/keystonejs/keystone/tree/docs-upgrade-gatsby |
I run into this and sometimes I just have to rerun it and it works. |
We're now validating if the path specified exists and throwing error if not. |
Hi, I've followed the examples provided in the readme but whenever I add the plugin and restart with gatsby develop, I just end up hanging in terminal on
success open and validate gatsby-config.js — 0.007 s
success copy gatsby files — 0.025 s
⠁ source and transform nodes
Not sure what else to try, Am I doing something massively wrong or is it a known issue?
This is my code from gatsby-config.js
Any help appreciated 👍
The text was updated successfully, but these errors were encountered: