Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[pull] canary from vercel:canary #193

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
merged 8 commits into from
Jun 4, 2025
Merged

[pull] canary from vercel:canary #193

merged 8 commits into from
Jun 4, 2025

Conversation

pull[bot]
Copy link

@pull pull bot commented Jun 4, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.1)

Can you help keep this open source service alive? 💖 Please sponsor : )

devjiwonchoi and others added 8 commits June 3, 2025 22:47
Style change in #80097 affected
style when adding the "Development Section" at
#80072. Therefore add the style
back to the section titles, and use "General" for the existing
preferernces.

| Before | After |
|--------|--------|
| ![CleanShot 2025-06-03 at 21 39
30@2x](https://github.com/user-attachments/assets/130825a9-6540-4c4b-ba1b-4c830e04382a)
| ![CleanShot 2025-06-03 at 21 39
17@2x](https://github.com/user-attachments/assets/3dc1444d-1588-4e4c-973a-ace88d501c95)
|
…0117)

This is a prerequisite for using https://github.com/boshen/cargo-shear, which uses `--all-features`. This also avoids some noise in Rust Analyzer, which also uses `--all-features`.
When you use sync IO in the client in a way that needs to be fixed we
currently still just provide you with the explanation for server
components. The fixes when sync IO happens in the client are not the
same as when they happen in a server component so this update adds
client specific documentation for these situations.

Namely, the key difference is that on the server you can add caching
through "use cache" and this is not available to you in the client. sync
IO in general is (going to be) allowed in client components broadly as
long as Next.js has a fallback UI to prerender. This means that "fixing"
sync IO access in the client will usually be solved by wrapping in a
Suspense boundary. The alternative is to move the sync IO out of render
or move it to the server where it can be cached.
…80121)

Remove unused dependencies to (hopefully) speed up the build.

https://github.com/boshen/cargo-shear

```
$ cargo shear --expand --exclude=wasm
Analyzing /home/bgw.linux/next.js

No unused dependencies!
```
@pull pull bot added the ⤵️ pull label Jun 4, 2025
@pull pull bot merged commit b981ac5 into code:canary Jun 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants