-
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
Refactoring module references #5572
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
10 Ignored Deployments
|
Logs
See job summary for details |
|
Linux Benchmark for 97b5dffClick to view benchmark
|
Linux Benchmark for 3d1c823Click to view benchmark
|
Linux Benchmark for 1e91e03
Click to view full benchmark
|
MacOS Benchmark for 1e91e03
Click to view full benchmark
|
Linux Benchmark for eaa2e91
Click to view full benchmark
|
MacOS Benchmark for eaa2e91
Click to view full benchmark
|
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.
There's a bunch of places where we should rename asset -> module, and a bunch of unnecessary Vc functions to clean up, but otherwise LGTM.
# Conflicts: # crates/turbopack-core/src/reference/mod.rs
Linux Benchmark for 913d518Click to view benchmark
|
MacOS Benchmark for 913d518
Click to view full benchmark
|
Linux Benchmark for 558489aClick to view benchmark
|
MacOS Benchmark for 558489a
Click to view full benchmark
|
### What? see vercel/turbo#5572 ### Why? ### How?
Description
Split
AssetReference
ResolveResult
into Module and Source variantssimplify ResolveResult
get rid of some temporary type fixup methods
graph references are now typed either Source, Module or OutputAsset instead of only Asset in general
next.js PR: vercel/next.js#52930