-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
fix(turbopack): add no-op resolveAbsolutePath
to browser runtime
#8549
base: main
Are you sure you want to change the base?
fix(turbopack): add no-op resolveAbsolutePath
to browser runtime
#8549
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Ignored Deployments
|
🟢 Turbopack Benchmark CI successful 🟢Thanks |
✅ This change can build |
|
1a084c1
to
1c3c3d7
Compare
if (modulePath) { | ||
return modulePath; | ||
} | ||
return "/ROOT/"; |
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.
Shoudn't it return something like:
if (modulePath) { | |
return modulePath; | |
} | |
return "/ROOT/"; | |
return `/ROOT/${modulePath || ''}`; |
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.
Yes, initially thought it was added by codegen
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.
Could you add a test case testing this behavior?
Description
Reading
import.meta.hot
should work in the browser, it can just return a/ROOT/...
path.Fixes vercel/next.js#66005