Add eagerness option description and example for prefetch()

[Marocco2]

Description (required)

As per request, I've added a new section for Prefetch docs page describing what the new option does and a use case that it would be useful

For Astro version: 5.6. See astro PR #13405

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	657ba25
🔍 Latest deploy log	https://app.netlify.com/sites/astro-docs-2/deploys/67ebe0adc1e781000842702b
😎 Deploy Preview	https://deploy-preview-11250--astro-docs-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[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

File	Note
en/guides/prefetch.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.

[astrobot-houston]

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉

Here’s what will happen next:

1. Our GitHub bots will run to check your changes.
   If they spot any broken links you will see some error messages on this PR.
   Don’t hesitate to ask any questions if you’re not sure what these mean!

2. In a few minutes, you’ll be able to see a preview of your changes on Netlify 🥳.

3. One or more of our maintainers will take a look and may ask you to make changes.
   We try to be responsive, but don’t worry if this takes a few days.

[sarah11918]

Thank you for submitting the docs for this great new feature, @Marocco2 ! I'm sure people will really appreciate having this!

I just made some editing suggestions to make this sound more like the rest of our docs and follow some of our styles. You are the expert in this topic, so please correct anything that's wrong, and make any suggestions back if something needs fixing!

[Marocco2]

Thank you for submitting the docs for this great new feature, @Marocco2 ! I'm sure people will really appreciate having this!

I just made some editing suggestions to make this sound more like the rest of our docs and follow some of our styles. You are the expert in this topic, so please correct anything that's wrong, and make any suggestions back if something needs fixing!

Thank you for taking your time making the changes! I found all of them reasonable, so I've merged them 👍

[sarah11918]

Thank you! From now on, these docs should not change too much, but probably just typos etc. In that case, I will commit small fixes directly so that you do not have to be bothered. 😄

[yanthomasdev]

Thanks, good work!

[sarah11918]

Would love a final approval from @Marocco2 here, as I added some stuff, so make sure this all still seems correct!

@ArmandPhilippot , I added the API reference at the top so couldn't hurt for you to confirm. 😄

Then, I think this is ready to merge into the 5.6.0 PR branch for this week's release! 🥳

[Marocco2]

Would love a final approval from @Marocco2 here, as I added some stuff, so make sure this all still seems correct!

@ArmandPhilippot , I added the API reference at the top so couldn't hurt for you to confirm. 😄

Then, I think this is ready to merge into the 5.6.0 PR branch for this week's release! 🥳

I've checked. All good 👍

[ArmandPhilippot]

@sarah11918 The API reference seems fine to me! However, I don't understand why, I can't see it in the preview (there is only Since):

Edit: I copied the changes locally to test, and this works fine with the dev server. So I guess it's just a bug in the preview?

[sarah11918]

@ArmandPhilippot It's because previews aren't generated for PRs not to the main branch! (I forget sometimes myself.) We can double double check once it's merged into the 5.6.0 PR, because that is made to the main branch. I switched target branches earlier than usual, because we're ahead of the game, but I forgot (myself) that we lose previews that way.