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(sentry): disable server wrapper #1733

Merged
merged 1 commit into from
Jan 26, 2025
Merged

fix(sentry): disable server wrapper #1733

merged 1 commit into from
Jan 26, 2025

Conversation

dargmuesli
Copy link
Member

📚 Description

The Nuxt server does not start with the current Sentry wrapper in production. There is no log indicating why. This disables the Sentry wrapper per default and keeps it as an alias for future debugging.

📝 Checklist

  • The PR's title follows the Conventional Commit format

The Nuxt server does not start with the current Sentry wrapper in production. There is no log indicating why. This disables the Sentry wrapper per default and keeps it as an alias for future debugging.
@dargmuesli dargmuesli merged commit 313ae5f into master Jan 26, 2025
8 checks passed
@dargmuesli dargmuesli deleted the fix/sentry/server branch January 26, 2025 21:59
maevsi-bot pushed a commit that referenced this pull request Jan 26, 2025
## [6.1.1](6.1.0...6.1.1) (2025-01-26)

### Bug Fixes

* **sentry:** disable server wrapper ([#1733](#1733)) ([313ae5f](313ae5f))
* **vite:** allow host `maevsi` ([#1731](#1731)) ([fe10465](fe10465))
@maevsi-bot
Copy link

🎉 This PR is included in version 6.1.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

2 participants