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.

Sign up for GitHub

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

Jump to bottom

PropType error from _error.js on no error pages #1056

Closed
khrome83 opened this issue Feb 9, 2017 · 1 comment · May be fixed by bgeveritt-snyk/next.js#15, bgeveritt-snyk/next.js#19, bgeveritt-snyk/next.js#20, bgeveritt-snyk/next.js#23 or bgeveritt-snyk/next.js#24
Closed

PropType error from _error.js on no error pages #1056

khrome83 opened this issue Feb 9, 2017 · 1 comment · May be fixed by bgeveritt-snyk/next.js#15, bgeveritt-snyk/next.js#19, bgeveritt-snyk/next.js#20, bgeveritt-snyk/next.js#23 or bgeveritt-snyk/next.js#24

Comments

@khrome83
Copy link
Contributor

khrome83 commented Feb 9, 2017

So I am using the error page example from the Readme.md.

I added propTypes to follow our ESLint standards. When loading / I get the follow error. When loading /page-does-not-exist I get no error. The issue is that React.propTypes is not found so string can not be resolved, yet I am importing React in the error file (like the example).

I would expect to get this issue when loading a error page, instead it shows for all files. Advice?

Uncaught TypeError: Cannot read property 'string' of undefined
    at Object.eval (eval at evalScript (eval-script.js?6d7f685:22), <anonymous>:90:40)
    at Object.581 (eval at evalScript (eval-script.js?6d7f685:22), <anonymous>:117:30)
    at __webpack_require__ (bootstrap 7a5f342…?09b487d:693)
    at fn (bootstrap 7a5f342…?09b487d:110)
    at Object.582 (eval at evalScript (eval-script.js?6d7f685:22), <anonymous>:125:18)
    at __webpack_require__ (bootstrap 7a5f342…?09b487d:693)
    at webpackJsonpCallback (bootstrap 7a5f342…?09b487d:23)
    at eval (eval at evalScript (eval-script.js?6d7f685:22), <anonymous>:2:1)
    at evalScript (eval-script.js?6d7f685:22)
    at Object.<anonymous> (next-dev.js?804dbaf:20)
@khrome83
Copy link
Contributor Author

khrome83 commented Feb 9, 2017

NM. Type-o that eslint plugin did not catch. Will file bug with them.

@khrome83 khrome83 closed this as completed Feb 9, 2017
@lock lock bot locked as resolved and limited conversation to collaborators May 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@khrome83