Open stephanie-anderson opened 9 months ago
If you need insights from the Nuxt team at any time, please don't hesitate to reach out! 🙏
This is such a great news!
It would be ideal that it would work on all envs. Nuxt works very well on the edge (cloudflare workers, netlify edge, etc), however not all libraries are compatible as there are some restrictions (no eval, no new Function(), etc).
It would be great if sentry/nuxt
would work everywhere from day one.
@cosbgn Thanks for the input! Which libraries do you mean with "not all libraries are compatible"?
@cosbgn Thanks for the input! Which libraries do you mean with "not all libraries are compatible"?
Hi @s1gr1d, I don't have an extensive list, but for example AJV doesn't work. Workers don't use node, they use their own runtime (workerd) which is limited to web standards (similarly to deno).
I think if you use only sentry/core
it should work as it's used by toucan-js which is an unofficial client for cloudflare workers. I think sentry/node won't work by default, but I might be wrong here.
This is of course for the backend part of nuxt, i.e. nitro. On the frontend sentry/vue should work perfectly.
I use Sentry on my APIs (fullstack Nuxt 3 deployment to Cloudflare pages) with the sentry/browser package on the API side to get around edge restrictions.
The context Sentry devs, for cosbgn's comment, is that Nuxt 3 was built with the "deploy anywhere" ethos, so all the core packages and (new) community modules are designed to be runtime agnostic. That's where https://unjs.io/ was born from.
I initially followed this guide if it helps at all with the PR in general https://www.lichter.io/articles/nuxt3-sentry-recipe (written by a core Nuxt 3 dev)
While we may not support worker (WinterCG) runtimes from the start we will look into it eventually. We are planning to release the SDK iteratively and in stages. Prioritization of worker runtime support depends of course a bit on the demand. I added an item to the list to track. Technically we have all the building blocks available.
I don't have any specific data, but from my understanding a big percent of nuxt apps are deployed on the edge (vercel-edge, workers, netlify edge, etc) as you get better performance for lower costs, and Nuxt pretty much "guarantees" that it will work on the edge, so it's an obvious solution.
I understand if you decide not to prioritize it, I just wanted to let you know that it would be great to have it from day one. It might be as simple as using sentry/core rather than sentry/node (I don't know, just an example).
Anyways, thanks for the first party package, love sentry and I would love to be able to add it to Nuxt easily!
New SDK for https://nuxt.com/
There is an existing discussion: Sentry SDK for Nuxt
Nuxt uses nitro as their server, this means we'll need to have nitro support. It might make sense for us to create an OpenTelemetry instrumentation for nitro. It will also be valuable to add similar instrumentation for the other libraries Nuxt relies on:
useError
composable