Replies: 1 comment 4 replies
-
|
@sgoodluck sorry don't really use Sentry, but I was wondering, have you tried this solution? #174 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
Yes indeed / that's our present workaround |
Beta Was this translation helpful? Give feedback.
-
|
I see, I'm glad that you could go that route 🙂 I am sorry that it's clearly not ideal, but I am not sure if we can do anything about it unless Vercel fixes/changes their implementation 😞 |
Beta Was this translation helpful? Give feedback.
-
|
I was just about to post this same finding and now I'm sad because this was posted back in April... I pinged Vercel on the other ticket |
Beta Was this translation helpful? Give feedback.
-
|
yeah... unfortunately the issue there isn't really getting much attention 😓 |
Beta Was this translation helpful? Give feedback.
-
Potentially related: #174
The logging tool, Sentry, seems to be incompatible with next-on-pages.
At least, when following their recommended documentation.
I suspect the incompatibility has to do with the _error component it generates.
NextJS _error page ref: https://nextjs.org/docs/advanced-features/custom-error-page
Is there a better way to do this where Sentry will be supported?
Has anyone successfully configured Sentry with a next deployment to CFP?
Beta Was this translation helpful? Give feedback.
All reactions