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.

Sign up for GitHub

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

Jump to bottom

Use the Sentry Nuxt module instead of our temporary implementation #5270

Open
obulat opened this issue Dec 11, 2024 · 0 comments
Open

Use the Sentry Nuxt module instead of our temporary implementation #5270

obulat opened this issue Dec 11, 2024 · 0 comments
Labels
💻 aspect: code Concerns the software code in the repository 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: frontend Related to the Nuxt frontend ⛔ status: blocked Blocked & therefore, not ready for work

Comments

@obulat
Copy link
Contributor

obulat commented Dec 11, 2024 •
edited
Loading

Problem

The Sentry module for Nuxt 3 is in Beta stage now. It is better to use it instead of the current implementation.

Edit: I tried the new module locally, and it can't build due to getsentry/sentry-javascript#14671. Blocked until that issue is fixed.

Description

Add Sentry module according to the instructions in the docs. Set up client, server and source map uploading.

Alternatives

Keep using the current setup. We cannot see the source map currently.

Additional context

When migrating to Nuxt 3, the Sentry module for Nuxt 3 wasn't released yet.
@obulat obulat added 💻 aspect: code Concerns the software code in the repository 🟨 priority: medium Not blocking but should be addressed soon 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🧱 stack: frontend Related to the Nuxt frontend labels Dec 11, 2024
@openverse-bot openverse-bot moved this to 📋 Backlog in Openverse Backlog Dec 11, 2024
@obulat obulat added the ⛔ status: blocked Blocked & therefore, not ready for work label Dec 12, 2024
@openverse-bot openverse-bot moved this from 📋 Backlog to ⛔ Blocked in Openverse Backlog Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
💻 aspect: code Concerns the software code in the repository 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: frontend Related to the Nuxt frontend ⛔ status: blocked Blocked & therefore, not ready for work
Projects
Openverse Backlog
Status: ⛔ Blocked
Milestone
No milestone
Development

No branches or pull requests
1 participant
@obulat