🐛 BUG: Empty Fragments used in expressions cause error in formatter

[The1stWii2]

Describe the Bug

Using the shorthand form of the JSX Fragment (<>...</>) as a part of an expression causes a syntax error in the formatter if it does not contain anything, despite being valid syntax.
E.g.,

---

---
<div>
  {false ? <p>This won't be formatted.</p> : <></>}
  {true && <></>}
  {false || <></>}  
  {[1,2,3].map(() => {
    return (<></>)
  })}
</div>

Compare that to

<div>
  {false ? <p>This won't be displayed.</p> : <>It will be formatted though.</>}
</div>

or

<div>
  {true && <Fragment/>}
</div>

or

<div>
  <></>
  And this shows it isn't empty Fragments in of themselves.
</div>

all of which do work.

Now in almost all of these scenarios it's not entirely clear why you'd even want an empty Fragment, but I personally stumbled across this bug because I tended to use empty Fragments for the else-side of ternaries (never been a big fan of condition && result).

Steps to Reproduce

1. npm init astro using template minimal template
2. Modify index page to include an empty Fragment in an expression, say,

<p>This document can't be formatted.</p>
      <div>
        {false ? <p>This won't be displayed.</p> : <></>}
      </div>

3. Open Command Palette and run Format Document.
4. Nothing happens (opening the output of the Astro Language Server reveals that it encountered a syntax error)

[MoustaphaDev]

That's an upstream compiler bug. Thanks for reporting!
Edit: I wrongly assessed it was, I'll maybe investigate again soon