compiler

What version of are you using? 2.13.1 (via , , ) What package manager are you using? npm What operating system are you using? macOS 15 (Darwin 25.5.0, Apple Silicon) Describe the Bug silently stops typing component props once a file crosses a 1-byte threshold in total comment mass. Past the cliff it emits instead of , and drops the whole block. is in both cases — the compiler reports nothing. Downstream, surfaces this as: which points at the one thing in the file that is provably correct. The obvious "fix" — deleting to silence the diagnostic — removes prop typing from the component for good. That is what makes this worth reporting: the visible symptom is a misleading diagnostic, but the actual damage is prop types silently degrading to in a file that still compiles and still ships. This looks related to #699 (same symptom, different trigger, fixed in 0.31.x). The trigger, bisected Two ingredients, both necessary in our file; neither is sufficient on its own in a synthetic file (see "what I could not reduce" below). 1. A tag name written inside a frontmatter block comment.* With `/ ... */mainxxxxRepro.astroxdeclare const Astro_props: Props---x` of the same length reproduces identically. Why the byte counts matter operationally Before we found this, our layout was sitting 81 bytes from the cliff, with no way to know. Any future comment — one sentence — would have silently dropped prop typing across every page of the site, and the error message would have sent whoever hit it to the wrong file.