Sync with react.dev @ 53fbed3f #465
Closed
Conversation
This file contains 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
…(#6445) * Fix: component not returned * Fix: missing function statement
Summary of changes: There is one "TypeScript strict mode" that is kept unchanged. Co-authored-by: xuan.huang <[email protected]>
Co-authored-by: Sebastian Silbermann <[email protected]>
this way "cannot be marked" is all the same style and you don't skim the link text and gloss over the "cannot be"
* fix(sandpack-template): use custom react sandpack template * refactor: Remove console.log statement Remove console.log(filePath); from createFileMap.ts * style: Update file paths in Sandpack components Update file paths in Sandpack components to use root folder and variables
* feat: add react india 2024 * update: move react india 2024 in date order * update: move conferences to past section * refactor: sort past conferences
…6496) * specify which sandbox files go in src directory * fix some stragglers
* Text Display error in Go full-stack with a framework Fix error #27816 What dose this PR do? It fixes the issue with the landing page of the react website. * Update HomeContent.js * Set styles on <option> * Add padding too --------- Co-authored-by: Ricky <[email protected]>
* Update use-server.md * revert export default
* fix wrong way quotes * bump up to clear mdx cache
Change untained -> untainted
* Update Feedback.tsx * Update Feedback.tsx Time reduced to 1.5 seconds, also going to update css * Update index.css CSS updated for feedback component animation. * Update Feedback.tsx * Update index.css --------- Co-authored-by: Ricky <[email protected]>
This reverts commit e18bb3b.
* Add React Conf 2024 Recap post * Spelling and links * Apply suggestions from code review Co-authored-by: lauren <[email protected]> * Edits * Edits * better link * Update date * Update date and nits * feedback --------- Co-authored-by: lauren <[email protected]>
* Add codemods to upgrade guide * Update src/content/blog/2024/04/25/react-19-upgrade-guide.md Co-authored-by: Ahmed Abdelbaset <[email protected]> * Add benefits --------- Co-authored-by: Ahmed Abdelbaset <[email protected]>
The docs for stylesheet precedence incorrectly state that there is an enumerated set of valid precedences. This is incorrect. The precedence value can be anything and React infers the hierarchy from the order in which it discovers precedences
* FIX: Typo in useEffect.md caveats * Fix another typo
* Add act documentation * Update structure based on feedback * Add usage examples and async act --------- Co-authored-by: Rick Hanlon <[email protected]>
Fix very minor typo
Added missing comma to the codesample.
Expo now has its own instructions for enabling the compiler.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically generated.
Merge changes from react.dev at 53fbed3
The following files have conflicts and may need new translations:
Please fix the conflicts by pushing new commits to this pull request, either by editing the files directly on GitHub or by checking out this branch.
DO NOT SQUASH MERGE THIS PULL REQUEST!
Doing so will "erase" the commits from main and cause them to show up as conflicts the next time we merge.