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

fix(gatsby): Make runtime error overlay work in non-v8 browsers #36365

Merged
merged 1 commit into from
Aug 11, 2022

Conversation

tyhopp
Copy link
Contributor

@tyhopp tyhopp commented Aug 11, 2022

Description

We currently use the stack-trace module for error parsing during gatsby develop. It is meant for use in Node.js environments, so it doesn't work in Safari and Firefox.

This PR makes a change to use the error-stack-parser, which has pretty much the same API and handles differences in browser Error objects.

Our existing e2e tests didn't catch this because we only test in Chrome. I'm opting not to add tests for this because we would need to (probably) migrate the existing tests to Playwright (Cypress does not support Safari) and also install multiple browser executables (which would add to our CI run time).

Documentation

N/A

Related Issues

Fixes #36362

[sc-54260]

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Aug 11, 2022
@tyhopp tyhopp added topic: core Relates to Gatsby's core (e.g. page loading, reporter, state machine) topic: DX Developer Experience (e.g. Fast Refresh, i18n, SSR, page creation, starters) and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Aug 11, 2022
@LekoArts LekoArts merged commit 2b4ff76 into master Aug 11, 2022
@LekoArts LekoArts deleted the fix-non-v8-browser-codeframes branch August 11, 2022 09:58
sunnyzanchi added a commit to newrelic/docs-website that referenced this pull request Jan 3, 2023
on `gatsby` 4.19.0, Firefox won't render the site in development
if there are any runtime errors. this was fixed in 4.21.0.
see gatsbyjs/gatsby#36365
sunnyzanchi added a commit to newrelic/docs-website that referenced this pull request Jan 3, 2023
* fix: upgrade `gatsby` to 4.21.0 to fix Firefox dev

on `gatsby` 4.19.0, Firefox won't render the site in development
if there are any runtime errors. this was fixed in 4.21.0.
see gatsbyjs/gatsby#36365

* upgrade Gatsby core dependencies to 4.21.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: core Relates to Gatsby's core (e.g. page loading, reporter, state machine) topic: DX Developer Experience (e.g. Fast Refresh, i18n, SSR, page creation, starters)
2 participants