-
Notifications
You must be signed in to change notification settings - Fork 47.2k
Issues: facebook/react
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[DevTools Bug] Could not find commit data for root "1"
Component: Developer Tools
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
Type: Bug
#31888
opened Dec 22, 2024 by
anwarrturay
[DevTools Bug]: Profiling not supported error with up-to-date React.
Component: Developer Tools
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
Type: Bug
#31880
opened Dec 20, 2024 by
patrickwalton
[DevTools Bug]: Profiling not supported error points to stale documentation link.
Component: Developer Tools
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
Type: Bug
#31878
opened Dec 20, 2024 by
patrickwalton
Bug: React 19 Build Error Report
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#31865
opened Dec 20, 2024 by
epicRipper
React 19 breaking with this.props.children
React 19
Resolution: Needs More Information
#31832
opened Dec 18, 2024 by
2xOu7
[React 19] Proposal: Enhancing useTransition Hook with Timed Start Transition Feature
React 19
#31830
opened Dec 18, 2024 by
rajaahsan365
Bug: Uncaught ReferenceError: MessageChannel is not defined
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#31827
opened Dec 18, 2024 by
Rados51
[React 19] Suspense throttling behavior (
FALLBACK_THROTTLE_MS) kicks in too often
React 19
Type: Discussion
#31819
opened Dec 17, 2024 by
uhyo
Bug: Potential Memory Leak - Detached elements after DOM Update due to state change
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#31818
opened Dec 17, 2024 by
cheng500
[React 19] The namespace type in @types/react/index.d.ts causes problems.
React 19
#31817
opened Dec 17, 2024 by
jin-Pro
Bug: Redundant Operation in getEntangledLanes Function Doesn't Modify entangledLanes as Intended
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#31816
opened Dec 17, 2024 by
Acabbage
Bug: Scheduler default time interval problem
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#31800
opened Dec 16, 2024 by
classmatewu
Bug: A potential issue that we haven't yet confirmed as a bug
eslint-plugin-react-compiler causes @babel/generator to console.log a message about import attributes on TS files
Status: Unconfirmed
#31793
opened Dec 15, 2024 by
abrahamguo
Bug: A potential issue that we haven't yet confirmed as a bug
use function doesn't warn about uncached promise when promise doesn't resolve immediately
Status: Unconfirmed
#31790
opened Dec 15, 2024 by
tomdohnal
[React 19] Incorrect infered response type in server actions with React 19
React 19
#31786
opened Dec 14, 2024 by
alexanderalmstrom
[React 19]
renderToString's output missing some rendered elements
React 19
#31754
opened Dec 13, 2024 by
Andarist
Bug: Replace md5 with sha256 in createFastHash().
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#31748
opened Dec 13, 2024 by
cryptochecktool
[React 19] [SUGGESTION] Consistency: Rename useFormStatus().pending to useFormStatus().isPending
React 19
#31747
opened Dec 12, 2024 by
hnordt
[Compiler Bug]: Handle TSInstantiationExpression expressions
Component: Optimizing Compiler
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
Type: Bug
#31745
opened Dec 12, 2024 by
artsiomshaitar
4 tasks
Bug: initial props will leak if a component renders nested elements, when an outer element never rerenders.
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#31744
opened Dec 12, 2024 by
onnlucky
[DevTools Bug] Cannot add node "1" because a node with that id is already in the Store.
Component: Developer Tools
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
Type: Bug
#31743
opened Dec 12, 2024 by
Nasrallah1997
[Compiler Bug]: Ref values may not be accessed during render when using A potential issue that we haven't yet confirmed as a bug
Type: Bug
mergeRefs
Component: Optimizing Compiler
Status: Unconfirmed
#31742
opened Dec 12, 2024 by
NeilTheFisher
1 of 4 tasks
Previous Next
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.