Skip to content

Comments

fix: Correctly parse mixed chrome/node renderer stack traces#509

Merged
timfish merged 3 commits intogetsentry:masterfrom
timfish:fix/node-renderer-stack
Jul 9, 2022
Merged

fix: Correctly parse mixed chrome/node renderer stack traces#509
timfish merged 3 commits intogetsentry:masterfrom
timfish:fix/node-renderer-stack

Conversation

@timfish
Copy link
Collaborator

@timfish timfish commented Jul 9, 2022

Closes #308

"cross-env": "^7.0.3",
"eslint": "7.27.0",
"electron": "15.3.0",
"electron": "19.0.8",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Intentional?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this is the version used for unit tests. If we don't keep this updated we can get dependabot security alerts.

This does mean we only run the unit tests in one Electron version but the e2e tests should keep on top of any breakages between Electron versions.

@timfish timfish merged commit 3bc2a2f into getsentry:master Jul 9, 2022
@timfish timfish deleted the fix/node-renderer-stack branch July 25, 2022 21:26
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

Successfully merging this pull request may close these issues.

Missing stacktrace in renderer process when using Node.js API integration

2 participants