docs: add preact devtools option

[florian-lefebvre]

Description (required)

Documents the addition of a devtools option for the preact integration.

Related issues & labels (optional)

• Closes #
• Suggested label: merge on release

For Astro version: 4.8. See astro PR #10938.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	May 8, 2024 3:55pm

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
docs-i18n	⬜️ Ignored (Inspect)		May 8, 2024 3:55pm

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale	File	Note
en	guides/integrations-guide/preact.mdx	Source changed, localizations will be marked as outdated.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[sarah11918]

Looks good @florian-lefebvre ! Just the same suggestions as in vue: to be a tiny bit more explicit in the text line and add the comonent, but good to go!

For reference:

Note that a new feature should include a <Since> component to display the version it was added in, and you'll need to check that this is also imported at the top of the page as import Since from '~/components/Since.astro';

(These integration pages used to be pulled from plain .md READMES in the astro repo, so they are often missing our nice components!)

[sarah11918]

D'oh! Our <Since /> component is hard-coded to say "astro" because it wasn't available for these other pages in our previous setup. Let me see whether it's easy enough for me to update the component to take an additional prop, or whether we just use Markdown to "fake" this (like we used to)

[sarah11918]

Approving for 4.8 release!

[sarah11918]

Updating branch and pointing to 4.8.0 branch!