Prettier fails / misparses <script> when conditionally rendered in .astro template expressions

[rutvikkaturi]

Astro Info

Astro                    v5.17.1
Vite                     v6.4.1
Node                     v22.14.0
System                   macOS (arm64)
Package Manager          pnpm
Output                   static
Adapter                  none
Integrations             astro-sitemap (v1.0.0)
                         astro-robots-txt (v1.0.0)

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

When a <script> tag is placed inside a conditional expression in an .astro file (ternary or &&), Prettier fails to format the file and throws a parsing error. The code compiles and runs correctly in both dev and build; the issue appears to be in Prettier parsing. This might be related to <script> being treated as a special Astro tag and not a normal JSX/HTML node when nested under expression containers.

Reproduction

1. Create a new Astro project
2. Install and enable prettier + prettier-plugin-astro
3. Add the following to a .astro file
4. Run Prettier on the file (Format Document / CLI)

---
const view = 'Gallery';
---

{view === 'Gallery' ? (
  <script>
    for (let index = 0; index < 10; index++) {
      console.log(index);
    }
  </script>
) : null}

{view === 'Gallery' &&
  (<script>
    for (let index = 0; index < 10; index++) {
      console.log(index);
    }
  </script>)
}

What's the expected result?

Prettier formats the file without errors, and preserves the script contents (or formats them consistently).

Link to Minimal Reproducible Example

Participation

• I am willing to submit a pull request for this issue.

[angelikatyborska]

I suspect this might be caused by the same root cause as #452

[rutvikkaturi]

Hi @angelikatyborska

After testing versions, I'm not sure this is the same root issue. I can reproduce a consistent failure starting at prettier-plugin-astro@3.1.0 (and continuing through 3.8.1). 3.0.0 doesn’t throw, but it also doesn’t format .astro files in my setup, so it may be skipping the parsing path entirely.

At this point I suspect the Astro Prettier plugin may simply not support (or not yet implement) the feature/pattern of an "optional" <script> tag being emitted inside a ternary/conditional render, e.g.:

{view === 'Gallery' ? (
  <script>
    for (let index = 0; index < 10; index++) {
      console.log(index);
    }
  </script>
) : null}

Prettier appears to be parsing the contents of that <script> as if it were part of the surrounding expression/markup, rather than treating it as an actual script payload — so it errors on the for (...) statement:

[error] apps/web/src/pages/[...path].astro: SyntaxError: Unexpected token (3:33)
[error]   1 | view === 'Gallery' ? (
[error]   2 |   <script>
[error] > 3 |     for (let index = 0; index < 10; index++) {
[error]     |                                 ^
[error]   4 |       console.log(index);
[error]   5 |     }
[error]   6 |   </script>

I also filed a related issue that looks like the same underlying gap: Astro VS Code extension loses syntax highlighting / IntelliSense for <script> when conditionally rendered (#15439) (withastro/astro#15439)

If it’s currently unsupported by design, it might be worth documenting (or tracking as a feature request) that inline <script> blocks inside ternary output aren’t handled yet.