add a link to my tutorial repo#13
Merged
petehunt merged 1 commit intofacebook:masterfrom May 30, 2013
Merged
Conversation
petehunt
added a commit
that referenced
this pull request
May 30, 2013
add a link to my tutorial repo
georgesisco
added a commit
to georgesisco/react
that referenced
this pull request
Apr 9, 2014
… steps The following steps also have an ajax function, but the 'error:' param is gone after facebook#13: facebook#14 facebook#17 facebook#19 facebook#20 This may be superfluous, but it helped me find an error with something I was doing - Namely, in my .json file, I had single line javascript comments ("//") that I copied from the tutorial. I couldn't find the issue on later steps, but was able to see my issue when the error handler complained about an unexpected "/" in my file in step facebook#13.
zpao
pushed a commit
that referenced
this pull request
May 8, 2014
The following steps also have an ajax function, but the 'error:' param is gone after #13: #14 #17 #19 #20 This may be superfluous, but it helped me find an error with something I was doing - Namely, in my .json file, I had single line javascript comments ("//") that I copied from the tutorial. I couldn't find the issue on later steps, but was able to see my issue when the error handler complained about an unexpected "/" in my file in step #13.
unstubbable
added a commit
to unstubbable/react
that referenced
this pull request
Jan 23, 2026
…ing (facebook#13) * [test] Use a busboy mock to have more control over field emission timing * No need for `nextTick` and avoid IIFE * No need to make the methods async
switz
added a commit
to switz/react
that referenced
this pull request
Mar 25, 2026
…ing (facebook#13) Added fused mode path to concurrent benchmark. Results show: - Fused is 1.0-1.6x faster than full pipeline (modest improvement) - But only 23-45% of Fizz-only ceiling (expected ~90%) - Heap pressure is much better: 66MB vs 284MB at c=50 - p95/p99 are comparable or worse due to serializeProps overhead Root cause: serializeProps runs processObject recursively for each of 226 product props at client boundaries, doing essentially the same serialization work Flight does. The CPU savings from eliminating Flight serialize/deserialize are offset by the hydration data serialization. The server-only path (no client boundaries) IS fast — 2300 req/s. The bottleneck is specifically the per-boundary props serialization. Also fixes: added client boundary function exports to legacy, markup, custom, and noop Fizz config forks (required for production build).
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.