-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Nextjs 13 app router in nx monorepo unable to build following sentry instructions #8798
Closed
3 tasks done
Labels
Comments
rvermootenct
changed the title
Nextjs 13 app router in nx monorepo
Nextjs 13 app router in nx monorepo unable to build following sentry instructions
Aug 11, 2023
lforst
added a commit
that referenced
this issue
Aug 11, 2023
Fixes #8798 In our logic that injects the Sentry config files to be executed, `path.relative()` may return something like `sentry.server.config.js` which is not allowed. Imports from the current directory need to start with './'. This is why we prepend the path with './', which should always again be a valid relative path.
Thanks for reporting this. I pushed a fix which we will release asap. Wondering why I didn't run into this in my test app.. |
Thank you @lforst please find GIF tax below: |
@lforst honestly so impressed in how quickly y'all jumped on this. Big kudos. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
7.63.0
Framework Version
13.4.4
Link to Sentry event
No response
SDK Setup
Steps to Reproduce
1.) Followed the instructions on manual installation (https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/ )
2.) Ran locally, was able to see crash reports.
3.) try to build
Expected Result
A build should be able to complete.
Actual Result
While building I get this error:
The middleware file aswell as the sentry files are in the root of the nextjs app.
The text was updated successfully, but these errors were encountered: