To fix the issue you can do Depending on how the index.html file is written, sometimes it’s not sufficient to open the file locally in a web browser—this can be true even if you’re not using Gatsby. Instead, sometimes it still needs to be served by a web server. What I imagine you’re seeing is that the index.html page works, but then some of the links are “broken” because they don’t point to the right places in the context of just opening the index.html file in your browser, but they actually will be correct in the real context of having the static site served by a web server.
it should still fix some issue The code below still serves the index.html page that's in the public folder, but I want to render index.ejs. I followed the video example so I'm not sure why he's able to render the ejs file whereas I'm still only seeing the index.html file. , Note that EJS by default looks into 'Views' folder
Hope this helps Actually it's working... But only when drag-and-droping public/ folder content at the server root, or at a specific path. For the latter, do not forget to specify the path prefix in gatsby-config.js:
it should still fix some issue As noted in the comments above the problem was that gatsby develop and gatsby build seemed to have different requirements. While working with the bulld command es6's fetch command needs to be imported manually (boo). This just meant adding the line