You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see that this path plus src/layouts or src/templates are hard coded directories in my project stack. The name src is conflicting with another src folder I have in my project. Therefore I wish there was a way I could designate a custom path for the folder I want gatsby to use for autogenerated pages.
component-page-creator.js is the file I supposed is responsible for this default behavior but when I introduced my change, the app broke. Other files of interest are
load-plugins.js
src/bootstrap/index.js
The way I thought about introducing the custom path was through the gatsby-config.js because its loaded on bootstrap however it broke the query-watcher.js when I save the file with a change.
What is the best way to introduce this custom path?
The text was updated successfully, but these errors were encountered:
I see that this path plus src/layouts or src/templates are hard coded directories in my project stack. The name src is conflicting with another src folder I have in my project. Therefore I wish there was a way I could designate a custom path for the folder I want gatsby to use for autogenerated pages.
component-page-creator.js
is the file I supposed is responsible for this default behavior but when I introduced my change, the app broke. Other files of interest areThe way I thought about introducing the custom path was through the
gatsby-config.js
because its loaded on bootstrap however it broke thequery-watcher.js
when I save the file with a change.What is the best way to introduce this custom path?
The text was updated successfully, but these errors were encountered: