-
Benachrichtigungen
You must be signed in to change notification settings - Fork 46.1k
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
Bug: Setting the state to the same value causes a re-render.
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#30558
opened Aug 1, 2024 by
JoonDong2
Bug: How do I synchronize my render function?
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#30543
opened Jul 31, 2024 by
parlay96
[Compiler Bug]: eslint-plugin-react-compiler reports "Hooks may not be referenced as normal values" if property begins "use"
Component: Optimizing Compiler
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
Type: Bug
#30493
opened Jul 28, 2024 by
lukpsaxo
1 of 4 tasks
TestUtils.Simulate alternatives
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#30478
opened Jul 26, 2024 by
georgylobko
Bug: When input type=number, input 1-1 cannot trigger an onchange and cannot be set to an empty string
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#30459
opened Jul 25, 2024 by
jzz2649
Bug: useState, state does not update inside websocket.onmessage rather the state value is preserved untill the next render
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#30454
opened Jul 25, 2024 by
nitesh-github143
Bug: deleting structure via DOM API breaks state updates
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#30444
opened Jul 24, 2024 by
hesxenon
Remove references to legacy class-based component architecture in error messages
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#30440
opened Jul 24, 2024 by
ADTC
[React 19] Omit the false value for custom element is an incorrect behaviour
React 19
#30418
opened Jul 22, 2024 by
PupilTong
Unexpected state behavior when updating nested state objects
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#30414
opened Jul 20, 2024 by
Sivanujan1998
FALLBACK_THROTTLE_MS slows tests down significantly - could it be configurable?
Type: Discussion
#30408
opened Jul 19, 2024 by
phryneas
Bug: useFormStatus pending state is reset when component state is updated
React 19
Type: Bug
#30368
opened Jul 18, 2024 by
jatwood
Bug: div: A potential issue that we haven't yet confirmed as a bug
ref is not a prop
Status: Unconfirmed
#30367
opened Jul 17, 2024 by
SaintPepsi
Feature Request: ESLint hooks rule for accessing previous state when deriving new state
Component: ESLint Rules
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#30363
opened Jul 17, 2024 by
Samuel-Therrien-Beslogic
Bug: effect runs with stale state values outside of Concurrent React
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#30291
opened Jul 8, 2024 by
denis-sokolov
Bug: Empty A potential issue that we haven't yet confirmed as a bug
style={} object values cause hydration warnings in React 18.3.1 - Includes solution
Status: Unconfirmed
#30163
opened Jul 1, 2024 by
nandastone
Bug: useEffect is triggered even if the array as dependency variable wasn't changed.
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#30141
opened Jun 29, 2024 by
enesgorkemgenc
[eslint-plugin-react-hooks] Missing type declarations
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
#30119
opened Jun 27, 2024 by
JstnMcBrd
Previous Next
ProTip!
What’s not been updated in a month: updated:<2024-07-01.