-
Notifications
You must be signed in to change notification settings - Fork 82
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
Sync with react.dev @ 9967ded3 #501
Conversation
* change isOpen variable in TopNav component to isMenuOpen to differentiate from isOpen props in Search component change setIsOpen to setIsMenuOpen in TopNav component * move initialization of ShowSearch state to top-level of TopNav component organize hook initializations in TopNav component: useState, useRef, useRouter * remove initialYScroll prop from DocSearchModal component to fix search functionality on ios devices
* Add docs for onCaughtError and onUncaughtError * Updates from feedback
Note that this component is not actually expandable and the ref got likely unused when that was removed
* in \[errorCode\].tsx, wrapped parsedContent in a div and applied styling of white-space: pre-wrap to preserve whitespace and break on newline chars * updated styling to tailwind class
Tickets are sold out, update the text.
* API docs for useDeferredValue's initialValue Updates the API docs for `useDeferredValue` to include the `initialValue` option, added in facebook/react#27500. This feature is slated for release in React 19. * Add docs for onCaughtError and onUncaughtError (#6742) * Add docs for onCaughtError and onUncaughtError * Updates from feedback * Add canary info, simplify a bit --------- Co-authored-by: Ricky <rickhanlonii@fb.com>
* Add documentation for ref cleanup functions * Contain changes within canary block
* move useFormState api * add redirect * use React DOM as the name
* Blog posts for React 19 * Feedback * Feedback * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <josh.c.story@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Noah Lemen <noah.lemen@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Matt Carroll <7158882+mattcarrollcode@users.noreply.github.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Matt Carroll <7158882+mattcarrollcode@users.noreply.github.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Noah Lemen <noah.lemen@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Noah Lemen <noah.lemen@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Noah Lemen <noah.lemen@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Noah Lemen <noah.lemen@gmail.com> * Update src/content/blog/2024/04/25/react-19.md * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Matt Carroll <7158882+mattcarrollcode@users.noreply.github.com> * Thanks * Apply suggestions from code review Co-authored-by: Matt Carroll <7158882+mattcarrollcode@users.noreply.github.com> Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com> * Feedback * nit * Issue link --------- Co-authored-by: Josh Story <josh.c.story@gmail.com> Co-authored-by: Noah Lemen <noah.lemen@gmail.com> Co-authored-by: Matt Carroll <7158882+mattcarrollcode@users.noreply.github.com> Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com>
* Typos in React 19 * Headings
should assign the result of updateName Co-authored-by: Tim Neutkens <tim@timneutkens.nl>
* Make use(Context) example easier to understand * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Ricky <rickhanlonii@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Ricky <rickhanlonii@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Ricky <rickhanlonii@gmail.com> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Ricky <rickhanlonii@gmail.com> --------- Co-authored-by: Ricky <rickhanlonii@gmail.com>
…s stable but the packages you work with as a framework and bundler will approach API stability (#6782)
Co-authored-by: Dom Zhu <dominic.zhu@uq.net.au>
* Better use(Promise) example in 19 blog * Better use(Promise) example in 19 blog
* Add rss feed * Add rss feed * rss readers don't like å characters
Change the tense of "build" to "building".
* Update synchronizing-with-effects.md Currently documentation says: By default, your Effect will run after every render. Which is in contrast with another section of the same page where it says: Effects run at the end of a commit after the screen updates * Update src/content/learn/synchronizing-with-effects.md --------- Co-authored-by: Ricky <rickhanlonii@gmail.com>
* Fix #6854: node.js version upgrade * Fix #6854: node.js version update
Co-authored-by: Rajat Jindal <rajat@testing.com>
* Update team.md: Jason Bonta * Update src/content/community/team.md Lauren's suggestion Co-authored-by: lauren <poteto@users.noreply.github.com> --------- Co-authored-by: lauren <poteto@users.noreply.github.com>
* Add initial skeleton * Scaffold compiler docs structure * Braindump for getting started * Add intro * tweaks * add experimental tag * flesh more out of index page * flesh out installation * add installation intro * update install instrs * add section on eslint plugin * reorg * add incremental guide * [debugging] Add section about devtools badge * [debugging] Add section about using logger * Update next.js instructions * reporting issues * [debugging] Add section on useEffect over firing * [debugging] Add section about conditional hook call * Latest updates * Remove ununsed reference pages * adding extra context for Remix --------- Co-authored-by: Sathya Gunasekaran <gsathya.ceg@gmail.com> Co-authored-by: Lauren Tan <poteto@users.noreply.github.com> Co-authored-by: Jason Bonta <jbonta@gmail.com>
Using "off", "warn", "error" has been supported for many years now - I think this helps improve the readability :) I completely forgot what rule: 2 meant - had to find it at https://eslint.org/docs/latest/use/configure/rules
Removed ; as it's unnecessary in jsx component
Front end nation is covering a full track of React talks including speakers such as: * Kent C Dodds * Sara Vieira * Tejas Kumar
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
Signed-off-by: Alessandro De Blasis <alex@deblasis.net>
Size changes📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
Page | Size (compressed) |
---|---|
global |
104.15 KB (🟡 +262 B) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script>
tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
Five Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
Page | Size (compressed) | First Load |
---|---|---|
/404 |
81.77 KB (🟡 +1.38 KB) |
185.92 KB |
/500 |
81.77 KB (🟡 +1.38 KB) |
185.92 KB |
/[[...markdownPath]] |
83.63 KB (🟡 +1.43 KB) |
187.78 KB |
/errors |
81.98 KB (🟡 +1.4 KB) |
186.13 KB |
/errors/[errorCode] |
81.96 KB (🟡 +1.41 KB) |
186.1 KB |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link
is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script>
tag are not accounted for in this analysis
Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 10% or more, there will be a red status indicator applied, indicating that special attention should be given to this.
This PR was automatically generated.
Merge changes from react.dev at 9967ded
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.