Skip to content

fix: ensure Sentry re-initializes in Dev after Nuxt config change#565

Merged
rchl merged 1 commit intomainfrom
fix/restart-dev
May 2, 2023
Merged

fix: ensure Sentry re-initializes in Dev after Nuxt config change#565
rchl merged 1 commit intomainfrom
fix/restart-dev

Conversation

@rchl
Copy link
Copy Markdown
Member

@rchl rchl commented May 1, 2023

Fixes #564

@rchl rchl force-pushed the fix/restart-dev branch from 012348c to 23408f9 Compare May 1, 2023 22:56
@rchl rchl force-pushed the fix/restart-dev branch from 23408f9 to 1fe2efd Compare May 1, 2023 22:56
@github-actions
Copy link
Copy Markdown

github-actions bot commented May 1, 2023

size-limit report 📦

Path Size
fixture: base 364.9 KB (0%)
fixture: lazy 369.3 KB (0%)
fixture: tracing 381.48 KB (0%)
fixture: lazy+tracing 385.85 KB (0%)

@rchl rchl changed the title fix: ensure sentry is re-initialized in dev mode after nuxt config change fix: ensure Sentry re-initializes in Dev after Nuxt config change May 2, 2023
@rchl rchl merged commit 5ee045d into main May 2, 2023
@rchl rchl deleted the fix/restart-dev branch May 2, 2023 07:05
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.

$sentry becomes unavailable after hard-reload during nuxt dev

1 participant