Whenever we recover from a parser error, we have to build an invalid AST so that the recovered error is actionable by other tools.
While implementing error recovery, I missed that when we find adjacent JSX nodes I was just throwing away a lot of AST nodes.

This is causing problems with Prettier because, when we parse <a/><b/>, we just generate the AST for the first JSX element and thus prettier doesn't re-print the second one.

I considered wrapping the two nodes with a "fake" fragment, but I decided not to do it because of ASI which doesn't work with JSX elements: in this example, I would want to insert a comma after the first JSX element rather than having a fragment.

const el = do {
  let x = <span>x</span>

  <div>{x}</div>
}