Fix edge case that caused odd panic error

[natemoo-re]

Changes

• User reported an inscrutable panic error
• I haven't been able to reproduce the specific situation that causes the panic, but I can see where the panic is happening.
• Doing a prerelease to confirm if this fixes the problem

Testing

I haven't figured out how to repro yet

Docs

N/A

[changeset-bot]

🦋 Changeset detected

Latest commit: 624bbe5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@astrojs/compiler	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[natemoo-re]

!preview no-panic

[github-actions]

 > root@0.0.0 release /home/runner/work/compiler/compiler > changeset publish "--tag" "next--no-panic" 🦋 warn ===============================IMPORTANT!=============================== 🦋 warn Packages will be released under the next--no-panic tag 🦋 warn ---------------------------------------------------------------------- 🦋 info npm info @astrojs/compiler 🦋 info @astrojs/compiler is being published because our local version (0.0.0-no-panic-20231221200720) has not been published on npm 🦋 info Publishing "@astrojs/compiler" at "0.0.0-no-panic-20231221200720" 🦋 success packages published successfully: 🦋 @astrojs/compiler@0.0.0-no-panic-20231221200720 🦋 Creating git tag... 🦋 New tag: @astrojs/compiler@0.0.0-no-panic-20231221200720

[natemoo-re]

!preview no-panic

[github-actions]

 > root@0.0.0 release /home/runner/work/compiler/compiler > changeset publish "--tag" "next--no-panic" 🦋 warn ===============================IMPORTANT!=============================== 🦋 warn Packages will be released under the next--no-panic tag 🦋 warn ---------------------------------------------------------------------- 🦋 info npm info @astrojs/compiler 🦋 info @astrojs/compiler is being published because our local version (0.0.0-no-panic-20231221204539) has not been published on npm 🦋 info Publishing "@astrojs/compiler" at "0.0.0-no-panic-20231221204539" 🦋 success packages published successfully: 🦋 @astrojs/compiler@0.0.0-no-panic-20231221204539 🦋 Creating git tag... 🦋 New tag: @astrojs/compiler@0.0.0-no-panic-20231221204539

[natemoo-re]

!preview no-panic

[github-actions]

 > root@0.0.0 release /home/runner/work/compiler/compiler > changeset publish "--tag" "next--no-panic" 🦋 warn ===============================IMPORTANT!=============================== 🦋 warn Packages will be released under the next--no-panic tag 🦋 warn ---------------------------------------------------------------------- 🦋 info npm info @astrojs/compiler 🦋 info @astrojs/compiler is being published because our local version (0.0.0-no-panic-20231221205336) has not been published on npm 🦋 info Publishing "@astrojs/compiler" at "0.0.0-no-panic-20231221205336" 🦋 success packages published successfully: 🦋 @astrojs/compiler@0.0.0-no-panic-20231221205336 🦋 Creating git tag... 🦋 New tag: @astrojs/compiler@0.0.0-no-panic-20231221205336

[natemoo-re]

@MoustaphaDev Well part of the problem here is that I'm trying to reproduce it and I'm unable to. CI might be able to catch it, though?

[MoustaphaDev]

Possibly, yes, if it's a platform specific issue

[torchsmith]

It was not working on Mac, and it was also not working on linux server.

[torchsmith]

If nate was testing on windows i wonder if it'd error out in ci or even in WSL

[natemoo-re]

Nope, I was also trying this on macOS, but I was isolating the file to just run it through the compiler...