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

Recover from solved errors in nested files without restarting develop #15719

Closed
karlhorky opened this issue Jul 15, 2019 · 2 comments
Closed

Comments

@karlhorky
Copy link
Contributor

karlhorky commented Jul 15, 2019

Summary

When errors occur within files within directories, the errors are reported on the command line and in the browser (this is good!). However, when the error has been resolved by removing the offending files, the errors do not go away.

Reproduction steps

  1. Start a new site using gatsby new
  2. Start the development server and navigate to a working page in the browser
  3. Add a folder under pages with a JavaScript with an error in it (for instance, import blah from 'blah' - an import of a non-existent package)
  4. The error appears in the browser and the command line
  5. Remove the folder again
  6. Refresh the page in the browser a bunch of times - the error appears intermittently until gatsby develop

Motivation

To prevent confusion about false negative error reporting.

Related

Maybe related to #14395

@karlhorky
Copy link
Contributor Author

Maybe this is more of a bug than a feature request actually...

@karlhorky karlhorky changed the title Recover from solved errors without restarting develop Recover from solved errors in nested files without restarting develop Jul 15, 2019
@karlhorky
Copy link
Contributor Author

Seems really like a bug, resubmitted as such: #15722

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant