menu
announcement

Spectrum will become read-only on August 10, 2021. Learn more about the decision in our official announcement.

Gatsby

Fast in every way that matters. Gatsby is a free and open source framework based on React that helps developers build blazing fast websites and apps.

Channels
# All channels
view-forward
# General
view-forward
# I Made This
view-forward
# Meta
view-forward
# Themes
view-forward
Team

Gatsby Build - Failed to load resource: net::ERR_FILE_NOT_FOUND

February 7, 2019 at 8:29am

Gatsby Build - Failed to load resource: net::ERR_FILE_NOT_FOUND

February 7, 2019 at 8:29am
Everything works fine with gatsby develop. When I run gatsby build and open the index.html, I get the following errors in my chrome console :
Failed to load resource: net::ERR_FILE_NOT_FOUND /app-c141937c2ffb16d548af.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND /12-c8bcf2beede8a33b73a6.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND /0-2d176e3d90599d6f73e0.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND /webpack-runtime-a98073cf1c88ed5ad79a.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND me-2cff084cc16aec8c535df04ec427e4aa.jpg:1 Failed to load resource: net::ERR_FILE_NOT_FOUND /static/d/173/path---index-6a9-NZuapzHg3X9TaN1iIixfv1W23E.json:1 Failed to load resource: net::ERR_FILE_NOT_FOUND /icons/icon-48x48.png:1 Failed to load resource: net::ERR_FILE_NOT_FOUND
All of the files above exist and have the correct path. Any help will be appreciated.

February 7, 2019 at 8:33am
This is most likely a webpack issue, i think recently gatsby had this issue, because the terser npm package (referenced by terser-webpack) made a critical change. You can try to upgrade gatsby and see if the issue is fixed. If the issue is not fixed can you paste a $ gatsby info --clipboard here. Also you can check for existing issues in the github repository, maybe create a new Issue on github?
  • reply
  • like
Thanks . I tried to upgrade gatsby and the issue persists.
  • reply
  • like
System: OS: macOS 10.14.2 CPU: (4) x64 Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz Shell: 3.2.57 - /bin/bash Binaries: Node: 10.15.0 - /usr/local/bin/node npm: 6.4.1 - /usr/local/bin/npm Browsers: Chrome: 71.0.3578.98 Safari: 12.0.2 npmPackages: gatsby: ^2.0.116 => 2.0.116 gatsby-image: ^2.0.29 => 2.0.29 gatsby-plugin-manifest: ^2.0.17 => 2.0.17 gatsby-plugin-offline: ^2.0.22 => 2.0.22 gatsby-plugin-react-helmet: ^3.0.6 => 3.0.6 gatsby-plugin-sharp: ^2.0.20 => 2.0.20 gatsby-plugin-styled-components: ^3.0.5 => 3.0.5 gatsby-source-filesystem: ^2.0.20 => 2.0.20 gatsby-transformer-sharp: ^2.1.13 => 2.1.13 npmGlobalPackages: gatsby-cli: 2.4.8
  • reply
  • like
Did you try a turn it off and then on again approach. In front end land that would be deleting your node_modules directory and then do a fresh npm install.
Edited
  • reply
  • like
Hi , unfortunately that didn't work. Thanks.
  • reply
  • like
Did you run gatsby serve?
  • reply
  • like

February 8, 2019 at 8:38am
Not sure what's the solution here there's an upstream issue, i believe originating from webpack (webpack-terser maybe?) I'm seeing issues with similar error report even on gatsby v2.0.118 I would suggest to scan trough issues for similar error reports maybe there's a temp. fix for your solution
Edited
  • reply
  • like