Chris Swithinbank

No, I don’t think so, sorry! Haven’t had time to maintain this really. There is an open PR here: https://github.com/delucis/bgio-effects/pull/564

I don’t really have the bandwidth to review, but if you can give it a review and leave comments, I could see if I remember how to release new versions...

Build failure was just a flakey run unrelated to this PR, here’s the re-run which passed: https://app.netlify.com/sites/astro-www-2/deploys/66c3baee388c8542555260e4

> `@tailwind` is a tailwind v3 thing AFAIK, is it still used in tailwind v4? Ah, not sure, perhaps not — can confirm we are using Tailwind v3 in this...

The Tailwind v4 upgrade guide suggests you're correct and `@tailwind` was removed: > In v4 you import Tailwind using a regular CSS `@import` statement, not using the `@tailwind` directives you...

Hi @oliwarner — thanks for asking! The footer is perhaps a bit misleading — I believe it may have been intended to refer to Astro the tool rather than the...

The virtual module shouldn’t make a difference here — that’s just needed to pass the user-configured image path to other parts of Starlight code. I think the following is happening:...

Closing this issue as I’m not sure we can easily fix this unfortunately — it would probably need fixing upstream in Astro.

Does Deno support running `astro build` now? If so, happy to look at a PR adding support for it if someone wants to make one!

I made a small extension that basically does your second suggestion — https://github.com/delucis/better-github-coauthors/ It adds an “Add co-authors” button to the merge UI that collects PR participants and appends a...