Skip to content
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

Uncaught "missing resources" error on 404 page #10534

Closed
chenders opened this issue Dec 18, 2018 · 0 comments
Closed

Uncaught "missing resources" error on 404 page #10534

chenders opened this issue Dec 18, 2018 · 0 comments
Labels
type: bug An issue or pull request relating to a bug in Gatsby

Comments

@chenders
Copy link

Description

When running gatsby develop with gatsby@2.0.66, navigating to a URL that doesn't exist (as suggested in part seven of the tutorial) results in a nice 404 page like this:

screen shot 2018-12-17 at 11 29 01 pm

Starting with gatsby@2.0.67, it results in an uncaught error:

screen shot 2018-12-17 at 11 34 14 pm

Looking through the comparison between the two versions, it looks like #10224 might be the culprit.

Steps to reproduce

  1. Create a new gatsby project from the hello world starter:
$  gatsby new testing-404 https://github.com/gatsbyjs/gatsby-starter-hello-world
  1. Install gatsby@2.0.66, run gatsby develop and see the proper 404 page
$ cd testing-404
$ yarn add gatsby@2.0.66
$ gatsby develop
# visit http://localhost:8000/sdf
  1. Stop gatsby-develop, install gatsby@2.0.67, run gatsby develop and note the uncaught error page
$ yarn add gatsby@2.0.67
$ gatsby develop
# visit http://localhost:8000/sdf

Expected result

404 page is displayed
screen shot 2018-12-17 at 11 29 01 pm

Actual result

Uncaught error is displayed
screen shot 2018-12-17 at 11 34 14 pm

Environment

 $ gatsby info --clipboard

  System:
    OS: macOS 10.14.2
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 11.3.0 - /usr/local/bin/node
    Yarn: 1.12.3 - /usr/local/bin/yarn
    npm: 6.4.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 71.0.3578.98
    Firefox: 63.0.3
    Safari: 12.0.2
  npmPackages:
    gatsby: 2.0.67 => 2.0.67 
  npmGlobalPackages:
    gatsby-cli: 2.4.6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug An issue or pull request relating to a bug in Gatsby
Projects
None yet
Development

No branches or pull requests

2 participants