Erika

Might not be needed in the future, changesets is fixing this issue https://github.com/changesets/changesets/pull/905

I investigated this a bit with my limited rollup, vite knowledge and here's where I got: Our compiler's `transform` returns the modules paths encoded, I first thought this was the...

Hello. I cannot reproduce this issue in the latest version of Astro. I suspect this was fixed by https://github.com/withastro/astro/pull/4344 Thank you for reporting this issue! If this rehappen to you,...

Hello! Is this currently in progress or something you want help with? I would gladly take this

Hey, I made a PR to their plugin to get this working: https://github.com/tailwindlabs/prettier-plugin-tailwindcss/pull/87 Hope we can get it merged! EDIT: PR got merged and it should be available in the...

Update on this, the main branch of the Tailwind plugin support Astro nicely, however the Tailwind team would like to find a more consistent way to support different frameworks before...

> This is sweet @Princesseuh! Can you post an update when the release is deployed? Yep, no worries! I'll post a message here and close this issue when they'll release...

The underlying issue that cause this is that the parser we use inside expressions since 0.5.0 is super good for everything but it does not support TypeScript correctly, unfortunately. Hoping...

> I imagine this is related to the JS block v.s. JS expression block confusion we were talking about the other day, right? https://discord.com/channels/830184174198718474/878341752799494154/1006912308867498175 Nope! This issue is specifically that...

> shouldn't this also format `astro` codeblocks in the markdown docs? Markdown files are currently excluded from formatting to avoid breaking the i18n process!