{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":783883919,"defaultBranch":"main","name":"react","ownerLogin":"fredyrogez","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2024-04-08T19:06:07.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/34008415?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1712603174.514237","currentOid":""},"activityList":{"items":[{"before":"ea6e05912aa43a0bbfbee381752caa1817a41a86","after":"2ba462b665bb4691067e67db3cfbffc56959b788","ref":"refs/heads/main","pushedAt":"2024-06-13T20:37:33.000Z","pushType":"push","commitsCount":134,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"[compiler][playground] Make change detection work in playground\n\nSummary: The change detection mode was unavailable in the playground because the pragma was not a boolean. This fixes that by special casing it in pragma parsing, similar to validateNoCapitalizedCalls\n\nghstack-source-id: 4a8c17d21ab8b7936ca61c9dd1f7fdf8322614c9\nPull Request resolved: https://github.com/facebook/react/pull/29889","shortMessageHtmlLink":"[compiler][playground] Make change detection work in playground"}},{"before":"ff60b11b1c649824904515a90ae27ad30efc5f60","after":"ea6e05912aa43a0bbfbee381752caa1817a41a86","ref":"refs/heads/main","pushedAt":"2024-05-28T07:26:19.000Z","pushType":"push","commitsCount":42,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"[Fiber] Enable Native console.createTask Stacks When Available (#29223)\n\nStacked on #29206 and #29221.\r\n\r\nThis disables appending owner stacks to console when\r\n`console.createTask` is available in the environment. Instead we rely on\r\nnative \"async\" stacks that end up looking like this with source maps and\r\nignore list enabled.\r\n\r\n\"Screenshot\r\n\r\nUnfortunately Chrome requires a string name for each async stack and,\r\nworse, a suffix of `(async)` is automatically added which is very\r\nconfusing since it seems like it might be an async component or\r\nsomething which it is not.\r\n\r\nIn this case it's not so bad because it's nice to refer to the host\r\ncomponent which otherwise doesn't have a stack frame since it's\r\ninternal. However, if there were more owners here there would also be a\r\n` (async)` which ends up being kind of duplicative.\r\n\r\nIf the Chrome DevTools is not open from the start of the app, then\r\n`console.createTask` is disabled and so you lose the stack for those\r\nerrors (or those parents if the devtools is opened later). Unlike our\r\nappended ones that are always added. That's unfortunate and likely to be\r\na bit of a DX issue but it's also nice that it saves on perf in DEV mode\r\nfor those cases. Framework dialogs can still surface the stack since we\r\nalso track it in user space in parallel.\r\n\r\nThis currently doesn't track Server Components yet. We need a more\r\nclever hack for that part in a follow up.\r\n\r\nI think I probably need to also add something to React DevTools to\r\ndisable its stacks for this case too. Since it looks for stacks in the\r\nconsole.error and adds a stack otherwise. Since we don't add them\r\nanymore from the runtime, the DevTools adds them instead.","shortMessageHtmlLink":"[Fiber] Enable Native console.createTask Stacks When Available (faceb…"}},{"before":"3f1436cca1f8dd80a19fd52b97b6ff71a4d9ce82","after":"ff60b11b1c649824904515a90ae27ad30efc5f60","ref":"refs/heads/main","pushedAt":"2024-05-18T14:44:55.000Z","pushType":"push","commitsCount":17,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"Add packageManager fields for Corepack compat (#29114)","shortMessageHtmlLink":"Add packageManager fields for Corepack compat (facebook#29114)"}},{"before":"9d76c954cfe134d7f541c3e706e344e6845ba235","after":"3f1436cca1f8dd80a19fd52b97b6ff71a4d9ce82","ref":"refs/heads/main","pushedAt":"2024-05-17T13:39:40.000Z","pushType":"push","commitsCount":1923,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"[compiler:playground] Fix broken builds\n\nNow that the compiler is public, the `*` version was grabbing the latest\nversion of the compiler off of npm and was resolving to my very first\npush to npm (an empty package containing only a single package.json).\nThis was breaking the playground as it would attempt to load the\ncompiler but then crash the babel pipeline due to the node module not\nbeing found.\n\nghstack-source-id: 695fd9caac64d15edfa095b8c871e75520381fcb\nPull Request resolved: https://github.com/facebook/react/pull/29122","shortMessageHtmlLink":"[compiler:playground] Fix broken builds"}},{"before":"ec15267a001086deb4ab5412d3f8b7e13573d6a5","after":"9d76c954cfe134d7f541c3e706e344e6845ba235","ref":"refs/heads/main","pushedAt":"2024-05-12T06:47:21.000Z","pushType":"push","commitsCount":15,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"[Flight] Error if a legacy React Element is attempted to be rendered (#29043)\n\nThis errors on the client normally but in the case the `type` is a\r\nfunction - i.e. a Server Component - it wouldn't be transferred to error\r\non the client so you end up with a worse error message. So this just\r\nimplements the same check as ChildFiber.","shortMessageHtmlLink":"[Flight] Error if a legacy React Element is attempted to be rendered (f…"}},{"before":"46abd7b1deb42d23b65480432609a2f8c5014cde","after":"ec15267a001086deb4ab5412d3f8b7e13573d6a5","ref":"refs/heads/main","pushedAt":"2024-05-08T07:35:40.000Z","pushType":"push","commitsCount":11,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"[Flight Reply] Resolve outlined models async in Reply just like in Flight Client (#28988)\n\nThis is the same change as #28780 but for the Flight Reply receiver.\r\n\r\nWhile it's not possible to create an \"async module\" reference in this\r\ncase - resolving a server reference can still be async if loading it\r\nrequires loading chunks like in a new server instance.\r\n\r\nSince extracting a typed array from a Blob is async, that's also a case\r\nwhere a dependency can be async.","shortMessageHtmlLink":"[Flight Reply] Resolve outlined models async in Reply just like in Fl…"}},{"before":"c7b1ae5a9ed58abece101d09c47ddd1e0b181fe2","after":"46abd7b1deb42d23b65480432609a2f8c5014cde","ref":"refs/heads/main","pushedAt":"2024-05-05T06:46:49.000Z","pushType":"push","commitsCount":14,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"Update `compiled-rn` destination paths to `vendor/react` (#28989)\n\nI'm changing the destination paths in fbsource from `vendor/*` to\r\n`vendor/react/*`.","shortMessageHtmlLink":"Update compiled-rn destination paths to vendor/react (facebook#28989"}},{"before":"d779eba4b375134f373b7dfb9ea98d01c84bc48e","after":"c7b1ae5a9ed58abece101d09c47ddd1e0b181fe2","ref":"refs/heads/main","pushedAt":"2024-05-02T16:02:42.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"[Tooling] Update critical artifact list (#28966)\n\nWhen a React PR is opened CI will report large size changes. But for\r\ncritical packages like react-dom it reports always. In React 19 we moved\r\nthe build for react-dom the client reconciler from react-dom to\r\nreact-dom/client\r\n\r\nThis change adds react-dom-client artifacts for stable and oss channels\r\nsince that is originally what was being tracked. But since\r\nreact-dom/client always imports react-dom I left the original react-dom\r\npackages as critical as well. They are small but it would be good to\r\nkeep an eye on them","shortMessageHtmlLink":"[Tooling] Update critical artifact list (facebook#28966)"}},{"before":"c4083616a232028588a2cbaa9ba8992481d1deb7","after":"d779eba4b375134f373b7dfb9ea98d01c84bc48e","ref":"refs/heads/main","pushedAt":"2024-04-30T06:27:54.000Z","pushType":"push","commitsCount":5,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"[react-native] Add unit test to ReactNativeAttributePayload (#28955)\n\n## Summary\r\n\r\nI'm looking at cleaning up some unnecessary manual property flattening\r\nin React Native and wanted to verify this behaviour is working as\r\nexpected, where properties from nested objects will always overwrite\r\nproperties from the base object.\r\n\r\n## How did you test this change?\r\n\r\nUnit tests","shortMessageHtmlLink":"[react-native] Add unit test to ReactNativeAttributePayload (facebook…"}},{"before":"6f18664b82b61d34b30c794a151d7b032f8eabe0","after":"c4083616a232028588a2cbaa9ba8992481d1deb7","ref":"refs/heads/main","pushedAt":"2024-04-26T06:32:55.000Z","pushType":"push","commitsCount":11,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"Create React 19 issue template","shortMessageHtmlLink":"Create React 19 issue template"}},{"before":"699d03ce1a175442fe3443e1d1bed14f14e9c197","after":"6f18664b82b61d34b30c794a151d7b032f8eabe0","ref":"refs/heads/main","pushedAt":"2024-04-24T11:57:06.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"eslint-plugin-react-hooks: Add support for ESLint v9 (#28773)","shortMessageHtmlLink":"eslint-plugin-react-hooks: Add support for ESLint v9 (facebook#28773)"}},{"before":"9defcd56bc3cd53ac2901ed93f29218007010434","after":"699d03ce1a175442fe3443e1d1bed14f14e9c197","ref":"refs/heads/main","pushedAt":"2024-04-23T08:38:29.000Z","pushType":"push","commitsCount":44,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"Cleanup `replayFailedUnitOfWorkWithInvokeGuardedCallback`and `enableProfilerNestedUpdateScheduledHook` (#28891)","shortMessageHtmlLink":"Cleanup replayFailedUnitOfWorkWithInvokeGuardedCallbackand `enableP…"}},{"before":"ba1a9797eebee694f6872e425b3a697c39a17dfc","after":"9defcd56bc3cd53ac2901ed93f29218007010434","ref":"refs/heads/main","pushedAt":"2024-04-13T09:32:36.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"Remove redundant props assign (#28829)","shortMessageHtmlLink":"Remove redundant props assign (facebook#28829)"}},{"before":"a2582074b84e95f8e9be6d9f51c80f09dd620ad7","after":"ba1a9797eebee694f6872e425b3a697c39a17dfc","ref":"refs/heads/main","pushedAt":"2024-04-12T17:13:56.000Z","pushType":"push","commitsCount":8,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"Remove `flight-browser` fixture (#28828)\n\nThe flight-browser fixtures doesn't make sense. It also uses UMD builds\r\nwhich are being removed so we'd have to make it use esm.sh or something\r\nand really it just won't work because it needs to be built by webpack to\r\nnot error. We could potentially shim the webpack globals but really the\r\nright thing is to publish the esm version of react-server and use esm.sh\r\nto load a browser only esm demo of react-server. This change removes the\r\nflight-browser fixture","shortMessageHtmlLink":"Remove flight-browser fixture (facebook#28828)"}},{"before":"ed3c65caf042f75fe2fdc2a5e568a9624c6175fb","after":"a2582074b84e95f8e9be6d9f51c80f09dd620ad7","ref":"refs/heads/main","pushedAt":"2024-04-11T16:22:34.000Z","pushType":"push","commitsCount":18,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"Fix nightly release job (#28824)","shortMessageHtmlLink":"Fix nightly release job (facebook#28824)"}},{"before":"9644d206e8d92d0e31a9252d78933a48c62eb427","after":"ed3c65caf042f75fe2fdc2a5e568a9624c6175fb","ref":"refs/heads/main","pushedAt":"2024-04-09T21:49:32.000Z","pushType":"push","commitsCount":10,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"Warn if outdated JSX transform is detected (#28781)\n\nWe want to warn if we detect that an app is using an outdated JSX\r\ntransform. We can't just warn if `createElement` is called because we\r\nstill support `createElement` when it's called manually. We only want to\r\nwarn if `createElement` is output by the compiler.\r\n\r\nThe heuristic is to check for a `__self` prop, which is an optional,\r\ninternal prop that older transforms used to pass to `createElement` for\r\nbetter debugging in development mode.\r\n\r\nIf `__self` is present, we `console.warn` once with advice to upgrade to\r\nthe modern JSX transform. Subsequent elements will not warn.\r\n\r\nThere's a special case we have to account for: when a static \"key\" prop\r\nis defined _after_ a spread, the modern JSX transform outputs\r\n`createElement` instead of `jsx`. (This is because with `jsx`, a spread\r\nkey always takes precedence over a static key, regardless of the order,\r\nwhereas `createElement` respects the order.) To avoid a false positive\r\nwarning, we skip the warning whenever a `key` prop is present.","shortMessageHtmlLink":"Warn if outdated JSX transform is detected (facebook#28781)"}},{"before":"6de7733e73152ecb9a0cb8bcf73dcc1c96ca7dde","after":"9644d206e8d92d0e31a9252d78933a48c62eb427","ref":"refs/heads/main","pushedAt":"2024-04-09T10:07:26.000Z","pushType":"push","commitsCount":12,"pusher":{"login":"fredyrogez","name":"Fredy Rogez","path":"/fredyrogez","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34008415?s=80&v=4"},"commit":{"message":"Soften useFormState warning (#28788)\n\nIt's not deprecated, it's really just renamed. Let's make the warning\r\nless scary.","shortMessageHtmlLink":"Soften useFormState warning (facebook#28788)"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEZNTPnAA","startCursor":null,"endCursor":null}},"title":"Activity · fredyrogez/react"}