Skip to content
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

The __debugSource attribute is missing from the React Fiber instance #65518

Closed
kblauhut opened this issue May 8, 2024 · 2 comments
Closed

The __debugSource attribute is missing from the React Fiber instance #65518

kblauhut opened this issue May 8, 2024 · 2 comments
Labels
bug Issue was opened via the bug report template. Developer Experience Issues related to Next.js logs, Error overlay, etc. locked

Comments

@kblauhut
Copy link

kblauhut commented May 8, 2024

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/quizzical-framework-53984p

To Reproduce

  1. Open the code sandbox
  2. Run the preview
  3. Open the console: You will see the React Fiber instance being logged there
  4. The __debugSource attribute is missing

Current vs. Expected behavior

NextJs used to provide the __debugSource attribute on the React Fiber instance. This contains information such as the folder path which is used by tools like click-to-component and react-dev-inspector to allow for a smoother dev experience.

While this has been an issue with server components for some time now (reported in this issue), starting with NextJs 14.2.0 this information is also missing from client components.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.3.0-canary.49 // Latest available version is detected (14.3.0-canary.49).
  eslint-config-next: 14.1.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.2
Next.js Config:
  output: N/A

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

Developer Experience

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

next dev (local)

Additional context

I tested reproducing this against multiple versions of NextJs and it seems that this issue was introduced with 14.2.0-canary.0

@kblauhut kblauhut added the bug Issue was opened via the bug report template. label May 8, 2024
@github-actions github-actions bot added the Developer Experience Issues related to Next.js logs, Error overlay, etc. label May 8, 2024
@kblauhut
Copy link
Author

This seems to be a change made to the latest version of React and is not related to NextJs directly: facebook/react#28265

Copy link
Contributor

github-actions bot commented Jun 2, 2024

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot added the locked label Jun 2, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template. Developer Experience Issues related to Next.js logs, Error overlay, etc. locked
Projects
None yet
Development

No branches or pull requests

1 participant