You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, there is an active issue on Sentry's NextJS adapter explaining that Turbopack loaders do not provide the necessary data for Sentry's NextJS plugin to work fully.
Are there any plans to support passing transpiled JS via the loader, or any interest on Vercel's end to help Sentry find ways to make their SDK work with NextJS's Turbopack pipeline? I imagine a lot of NextJS users use Sentry so this could stop a lot of teams from ultimately moving to Turbo, mine included.
(Relatedly, on that issue, this unplugin issue (unjs/unplugin#302) is referenced, highlighting Turbopack's plugin system lacks APIs necessary for that project to support Turbopack as well)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, there is an active issue on Sentry's NextJS adapter explaining that Turbopack loaders do not provide the necessary data for Sentry's NextJS plugin to work fully.
getsentry/sentry-javascript#8105 (comment)
Are there any plans to support passing transpiled JS via the loader, or any interest on Vercel's end to help Sentry find ways to make their SDK work with NextJS's Turbopack pipeline? I imagine a lot of NextJS users use Sentry so this could stop a lot of teams from ultimately moving to Turbo, mine included.
(Relatedly, on that issue, this
unpluginissue (unjs/unplugin#302) is referenced, highlighting Turbopack's plugin system lacks APIs necessary for that project to support Turbopack as well)Beta Was this translation helpful? Give feedback.
All reactions