Sasha Aickin

@Becavalier Thanks for the response! I'm pretty sure that the use cases for binary AST and WebAssembly are going to be pretty different, at least in the current landscape. It's...

@Qix- Great question; I haven't thought about it deeply, but I'll sketch out my rough ideas. So, there are a couple of ways to use `Accept`. The simplest way would...

Great point that `Accept-Encoding` has a similar set of issues! > an agent doesn't have to support encoding (compression) on all requests, and you can't be certain they do for...

@kannanvijayan Thanks for the response! > Am I forgetting anything? It's a good list, including several cases I hadn't thought of. I'd add: 5. HTTP/2 server push 6. `` 7....

@ljharb I haven't seen any of those links, and my Google-fu is failing me (spent about 10 minutes searching); would love a pointer if you have it easily at hand....

@ljharb > There is a difference, though, between distinguishing parsing goals, and distinguishing spec versions. To be clear, my last post was not saying that the existence of `nomodule` meant...

FYI, I'm currently porting over the ~550 server rendering tests I wrote for `react-dom-stream` into react master. A PR with the first 16 tests was accepted into react today, and...

@cescoferraro Thanks for the contribution. I was thinking of a similar wrapper as well. The one thing I'm not clear about is if `template` will render a React Element that...

How would you bypass it? Pass in a manifest at the command line? One other thing to note: I intended but never implemented a safety check here, where the `hash`...

Just so we are all on the same page: `manifest.json` is **required** on the server-side because it contains the names of the chunks with their content hashes. Without `manifest.json`, all...