Skip to content

[pull] canary from vercel:canary #251

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 3 commits into from
Aug 4, 2025
Merged

[pull] canary from vercel:canary #251

merged 3 commits into from
Aug 4, 2025

Conversation

pull[bot]
Copy link

@pull pull bot commented Aug 4, 2025

See Commits and Changes for more details.


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

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

mischnic and others added 3 commits August 4, 2025 12:08
Part of PACK-4164

~~Set `NODE_ENV` in tracing context~~ For that, see #75254 (comment)
Set `TURBOPACK` in tracing context

This get rids of some constant build overhead (because we only analyze one instance of react-dom for NFT now, instead of all of the edge/server/client onces).
Otherwise no measureable perf/memory impact
When implementing the check that disallows using `next/root-params` in
server actions, i forgot that when a page is rerendered after an action,
the render is still wrapped with an `actionAsyncStorage` with
`actionStore.isAction === true`. The fix is to also check that we're in
the `'action'` phase, i.e. we haven't switched to rendering yet.

Closes #82302
@pull pull bot locked and limited conversation to collaborators Aug 4, 2025
@pull pull bot added the ⤵️ pull label Aug 4, 2025
@pull pull bot merged commit 5bb867a into code:canary Aug 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants