-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[Windows] TypeError
when running Next.js app with middleware and latest @sentry/nextjs package
#6858
Comments
Have confirmed that this issue is still present when the |
@josh- That looks super fishy. Can you try deleting your |
Also just want to make sure you called your config files the following:
and not
|
Yep, same result:
We've also been able to reproduce this on several different windows machines who are cloning the issue reproduction repository fresh (and in our internal app where we initially ran into this) |
Can confirm they are named correctly in the issue reproduction repository (and also our internal app):
|
TypeError
when running Next.js app with middleware and latest @sentry/nextjs packageTypeError
when running Next.js app with middleware and latest @sentry/nextjs package
Ah sorry took me way longer to understand this issue happens on windows than it should have 😬 We'll look into it! |
@josh- Weird ask but can you try replacing line 71 in - test: /node_modules\/@sentry\/nextjs/,
+ test: /node_modules[\/\\]@sentry[\/\\]nextjs/, and try building your project again? Thank you! |
I had this error
This fixed the issue. |
Thanks @lforst 👍 Confirming also this fixes the issue. |
Thanks for confirming @memmen @josh-! We have a fix on its way. It will probably come with a new version on Monday. We avoid releasing on Fridays and Thursdays because we don't like working on the Weekends and all in case there is something going wrong badly. I recommend downgrading to 7.29.0 until then! |
came here for the same issue. i fixed it by disabling middleware instrumentation on dev sentry: {
autoInstrumentMiddleware: !!(
process.env.SENTRY_DSN || process.env.NEXT_PUBLIC_SENTRY_DSN
),
disableServerWebpackPlugin:
!process.env.SENTRY_DSN && !process.env.NEXT_PUBLIC_SENTRY_DSN,
disableClientWebpackPlugin:
!process.env.SENTRY_DSN && !process.env.NEXT_PUBLIC_SENTRY_DSN,
hideSourceMaps: true,
}, |
I'm still seeing this error using Here's my repo: https://github.com/lukevella/rallly/tree/update-sentry |
@lukevella Thanks for providing that repo! It helped identifying a regression in the last release. We are in the process of releasing a patch with a fix. Side-note: Sorry about all these issues with the SDK. We're doing some pretty ambitious stuff to support every feature and it's gotten a little bit fragile. I hope it won't take too long to mature! |
Will this next patch fix an error I am seeing with latest version (and does this relate to the above)? Getting this with
Currently causing Vercel builds to fail. Can open a new issue if this doesn't relate to this. |
@wadehammes Yeah that should be fixed with version |
I can confirm that this issue seems to be fixed in |
@lukevella Thanks for checking! |
@lforst also confirm that the error I was experiencing is fixed in latest |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which package are you using?
@sentry/angular
SDK Version
7.31.1
Framework Version
@sentry/nextjs 7.31.1
Link to Sentry event
https://sentry.io/organizations/triton-digital-canada-inc/issues/3883394829/
SDK Setup
The sample repro repository uses the following values, where the error still occurs.
sentry.client.config.js
:sentry.client.edge.js
:sentry.client.server.js
:Steps to Reproduce
yarn install
yarn dev
Expected Result
Page is rendered successfully.
Actual Result
This could be related to #6771? (cc @lforst)
Confirmed that it works as expected with v7.29.0
The text was updated successfully, but these errors were encountered: