-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Reorganize next_client and next_server modules #3182
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
kodiakhq
merged 1 commit into
main
from
alexkirsz/web-374-re-organize-next_client-and-next_server
Jan 6, 2023
Merged
Reorganize next_client and next_server modules #3182
kodiakhq
merged 1 commit into
main
from
alexkirsz/web-374-re-organize-next_client-and-next_server
Jan 6, 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 ↗︎
6 Ignored Deployments
|
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
c2118c4
to
a6720b1
Compare
Benchmark for 923e1a2Click to view benchmark
|
🟢 CI successful 🟢Thanks |
a6720b1
to
ccfa77b
Compare
Benchmark for 4495cc2Click to view benchmark
|
wbinnssmith
approved these changes
Jan 5, 2023
ccfa77b
to
9f0b183
Compare
Benchmark for 44aaff4Click to view benchmark
|
jridgewell
pushed a commit
to vercel/next.js
that referenced
this pull request
Mar 10, 2023
This is a straightforward chore PR to move next_client and next_server modules around, in order to make navigation and imports more predictable between them. I'm also planning to introduce a next_shared::context in a further PR, hence the changes.
sokra
pushed a commit
to vercel/next.js
that referenced
this pull request
Mar 13, 2023
This is a straightforward chore PR to move next_client and next_server modules around, in order to make navigation and imports more predictable between them. I'm also planning to introduce a next_shared::context in a further PR, hence the changes.
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 25, 2024
This is a straightforward chore PR to move next_client and next_server modules around, in order to make navigation and imports more predictable between them. I'm also planning to introduce a next_shared::context in a further PR, hence the changes.
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
This is a straightforward chore PR to move next_client and next_server modules around, in order to make navigation and imports more predictable between them. I'm also planning to introduce a next_shared::context in a further PR, hence the changes.
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.
This is a straightforward chore PR to move next_client and next_server modules
around, in order to make navigation and imports more predictable between them.
I'm also planning to introduce a next_shared::context in a further PR, hence the
changes.