-
Notifications
You must be signed in to change notification settings - Fork 2.1k
decode magic identifiers in error overlay #3433
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
Merged
ForsakenHarmony
merged 1 commit into
main
from
hrmny/web-430-error-overlay-decode-magic-identifiers
Jan 26, 2023
Merged
decode magic identifiers in error overlay #3433
ForsakenHarmony
merged 1 commit into
main
from
hrmny/web-430-error-overlay-decode-magic-identifiers
Jan 26, 2023
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Ignored Deployments
|
Current dependencies on/for this PR: This comment was auto-generated by Graphite. |
Benchmark for ccd2996Click to view benchmark
|
🟢 CI successful 🟢Thanks |
jridgewell
approved these changes
Jan 25, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does this look like?
TypeError: {imported module [project-with-next]/apps/vercel-site/lib/sentry.ts}.withScope is not a function instead of TypeError: __TURBOPACK__imported__module__$5b$project$2d$with$2d$next$5d2f$apps$2f$vercel$2d$site$2f$lib$2f$sentry$2e$ts__.withScope is not a function |
ijjk
pushed a commit
to vercel/next.js
that referenced
this pull request
Jan 26, 2023
**Note**: This requires #45314, otherwise the following error is shown, but does not block builds: ``` error - [build] examples/create-app Error evaluating Node.js code TypeError: makeResolver is not a function at getResolveRoute (path/to/next.js/examples/create-app/.next/build/chunks/router.js:21:18) at async Module.route (path/to/next.js/examples/create-app/.next/build/chunks/router.js:24:36) at async Module.run (path/to/next.js/examples/create-app/.next/build/chunks/[turbopack-node]_ipc_evaluate.ts.js:19:39) ``` ### Features - vercel/turborepo#3446 - vercel/turborepo#3396 - vercel/turborepo#3499 ### Bug fixes - vercel/turborepo#3433 ### Misc - vercel/turborepo#3479
jridgewell
pushed a commit
to vercel/next.js
that referenced
this pull request
Mar 10, 2023
sokra
pushed a commit
to vercel/next.js
that referenced
this pull request
Mar 13, 2023
ForsakenHarmony
added a commit
to vercel/next.js
that referenced
this pull request
Jul 25, 2024
ForsakenHarmony
added a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
ForsakenHarmony
added a commit
to vercel/next.js
that referenced
this pull request
Aug 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.