Sync with react.dev @ 11cb6b59 by react-translations-bot · Pull Request #109 · reactjs/is.react.dev
and others added 30 commits
December 16, 2024 16:05the “Dealing with rejected Promises” codesandbox example depends on react-error-boundary, but doesn’t specify it as a dependency, so the code example is broken
… React Native (#7369) * docs[compiler]: clarify React DevTools support for Compiler Badges in React Native * Update react-compiler.md * Update react-compiler.md --------- Co-authored-by: dan <dan.abramov@gmail.com>
* fix: remove forwardref from useImperativeHandle docs * Make changes more focused * Update useImperativeHandle.md --------- Co-authored-by: dan <dan.abramov@gmail.com>
In the section "Importing Server Functions from Client Components" updated "createNoteAction" to "createNote" to match the function name in the example
Co-authored-by: Sebastian Markbåge <sebastian@calyptus.eu> Co-authored-by: Rick Hanlon <rickhanlonii@fb.com> Co-authored-by: eps1lon <sebastian.silbermann@vercel.com>
Previously, `createFileMap` split the MDX meta string on spaces and assumed the first token was the filename. Once we prefixed code fences with `{expectedErrors: ...}`, it would incorrectly parse the meta and crash.
This PR updates createFileMap to skip tokens in the meta containing a start and end brace pair (using a stack to ensure we close on the correct brace) while tokenizing the meta string as expected.
Test plan: pages reported in #7994 no longer crash on the next PR
Closes #7994
For local dev and CI we want to have the eslint-local-rules running, so let's make sure both have their dependencies installed. We don't use a monorepo setup here, which is why they're currently setup as a two completely independent yarn workspaces.
* Update useEffectEvent docs for canary * Clean up prefixed imports * Fix import * Update blog post link
* Docs for `cacheSignal` * Apply suggestion from review Co-authored-by: Sebastian Markbåge <sebastian@calyptus.eu> * Apply suggestion from review Co-authored-by: Sebastian Markbåge <sebastian@calyptus.eu> * Update src/content/reference/react/cacheSignal.md --------- Co-authored-by: Sebastian Markbåge <sebastian@calyptus.eu>
* docs: scaffold docs structure for Performance tracks * docs: initial draft of Tracks section * refactor: moved to reference root section and added to the sidebar * chore: updated to canary and minor changes
* Init PPR docs * Overhaul * Apply suggestions from code review --------- Co-authored-by: Sebastian Sebbie Silbermann <sebastian.silbermann@vercel.com>
* wip * feedback and rm canary stuff * tweak * fix json * more canary stuff * fix link * update dates * update meta description * Expand performance track section * adjust linter note * edit perf tracks down * edit perf tracks down more * tweak note * tweak useEffectEvent * formatting * tweaks * ppr * rm canary stuff * fix json * fix json * tweaks * linter note * nit * nit * link * nit * ppr * missing await * add lint v6 * fix link --------- Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
We're updating eslint-plugin-react-hooks with support for useEffectEvent usage and updated configuration options for applying the useEffectEvent and other effect rules to custom effect hooks. This adds the documentation for the config syntax and adds mention to the useEffectEvent reference page that the linter should be used to ensure proper usage of Effect Events.
* Use stable release in demos with HTML output * Fix Activity sandboxes (#8035) * Fix Activity sandboxes * hacky fix * Revert "Fix Activity sandboxes (#8035)" This reverts commit f9fd07c. * Bump to 19.2 * cleanup rest of sandpacks * Pin deps * Add back package.json with third-party deps * "^" should be fixed now * add back package.json for more toastify deps * fuggin whitespace * more fuggin whitespace * fml like fr fr --------- Co-authored-by: Sebastian Sebbie Silbermann <sebastian.silbermann@vercel.com> Co-authored-by: Ricky <rickhanlonii@gmail.com> Co-authored-by: Rick Hanlon <rickhanlonii@meta.com>
Updates all mentions of eslint-plugin-react-hooks rc and 6.1.0 to refer to the new 6.1.1 which has important bugfixes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters