Skip to content

fix(remix): Export no-op as captureRemixServerException from client SDK #12497

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

Merged

Conversation

onurtemizkan
Copy link
Collaborator

Resolves #9594

@onurtemizkan onurtemizkan marked this pull request as ready for review June 14, 2024 16:35
@onurtemizkan onurtemizkan marked this pull request as draft June 14, 2024 16:35
@onurtemizkan onurtemizkan force-pushed the onur/export-no-op-for-captureRemixServerException branch from 0e29e0d to eb3aa8f Compare June 14, 2024 16:35
@onurtemizkan onurtemizkan force-pushed the onur/export-no-op-for-captureRemixServerException branch from eb3aa8f to 878d338 Compare June 17, 2024 13:32
@onurtemizkan onurtemizkan marked this pull request as ready for review June 17, 2024 13:32
@AbhiPrasad AbhiPrasad merged commit a98ad0f into develop Jun 17, 2024
89 checks passed
@AbhiPrasad AbhiPrasad deleted the onur/export-no-op-for-captureRemixServerException branch June 17, 2024 17:31
AbhiPrasad pushed a commit that referenced this pull request Jun 24, 2024
Marks `isRemixV2` as optional in the exposed types of
`captureRemixServerException`.

This is a follow-up on
#12497
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.

"captureRemixServerException" is not exported by "node_modules/@sentry/remix/esm/index.client.js"
3 participants