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

Skip to content

NextJS 15.3.1 broke the React Compiler #78867

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.

Sign up for GitHub

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

Jump to bottom
Closed
Daniel3711997 opened this issue May 6, 2025 · 0 comments · Fixed by #78874
Closed

NextJS 15.3.1 broke the React Compiler #78867

Daniel3711997 opened this issue May 6, 2025 · 0 comments · Fixed by #78874
Assignees
@kdy1

Comments

@Daniel3711997
Copy link

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/interesting-bird-tkf7lw

To Reproduce

Just run the app and use the React Dev Tools to see which components are memoized.

Current vs. Expected behavior

Expect that the React compiler to work

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Thu Mar  6 22:00:07 PST 2025; root:xnu-10063.141.1.704.6~1/RELEASE_ARM64_T6030
  Available memory (MB): 18432
  Available CPU cores: 12
Binaries:
  Node: 22.15.0
  npm: 10.9.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.3.1 // Latest available version is detected (15.3.1).
  eslint-config-next: N/A
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.8.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

This is the pull request that caused the issue: #78260
@kdy1 kdy1 self-assigned this May 6, 2025
This was referenced May 6, 2025
Merged
Merged
ijjk pushed a commit that referenced this issue May 6, 2025
@kdy1
fix(react-compiler): Fix detection of interest (#78874)
4cde29c 
### What?

Mark function components declared as a variable interesting

### Why?

Because those are also React Components

### How?

 - Closes SWC-646
-  Closes #78867
ijjk pushed a commit that referenced this issue May 6, 2025
@kdy1 @ijjk
fix(react-compiler): Fix detection of interest (#78874)
b9779e6 
### What?

Mark function components declared as a variable interesting

### Why?

Because those are also React Components

### How?

 - Closes SWC-646
-  Closes #78867
kdy1 added a commit to swc-project/swc that referenced this issue May 6, 2025
@kdy1
fix(es/react-compiler): Mark function components declared as a var in…
5eac076 
…teresting (#10437)

**Related issue:**

 - vercel/next.js#78867
eps1lon pushed a commit that referenced this issue May 7, 2025
@kdy1 @eps1lon
fix(react-compiler): Fix detection of interest (#78874)
80b30d2 
### What?

Mark function components declared as a variable interesting

### Why?

Because those are also React Components

### How?

 - Closes SWC-646
-  Closes #78867
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kdy1 kdy1

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(react-compiler): Fix detection of interest vercel/next.js
2 participants
@kdy1 @Daniel3711997