Feat/environment api

[ematipico]

Changes

• What does this change?
• Be short and concise. Bullet points can help!
• Before/after screenshots can help as well.
• Don't forget a changeset! Run pnpm changeset.
• See https://contribute.docs.astro.build/docs-for-code-changes/changesets/ for more info on writing changesets.
• Closes Use Vite's Environment API #14363

Testing

Docs

[changeset-bot]

🦋 Changeset detected

Latest commit: 21d819d

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

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

[codspeed-hq]

CodSpeed Performance Report

Merging #14306 will not alter performance

_{Comparing feat/environment-api (28b2f42) with main (f59581f)¹}

Summary

✅ 6 untouched

Footnotes

1. No successful run was found on next (16bb9f0) during the generation of this report, so main (f59581f) was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[github-actions]

📝 Changeset Validation Results

❌ Changeset validation failed

Issues Found:

.changeset/open-monkeys-boil.md

Issue with: 'Runs "astro dev" using Cloudflare Vite plugin. This means that dev runs in workerd, giving a dev experience much closer to production.'

❌ Errors:
• The description does not include actionable migration advice or sufficient details about the breaking change.
• The description does not match the required detail level for a major change type.

💡 Suggestions:
• Expand on the implications of "Runs astro dev using Cloudflare Vite plugin" and provide clear instructions to users on adapting to the new behavior.
• Include detailed migration steps or compatible alternatives to changes prompted by this update.

Issue with: 'TODO: add a lot more detail on what this means and what it breaks'

❌ Errors:
• The presence of a "TODO" implies incomplete information.
• Unfinished details do not conform to required guidelines.

💡 Suggestions:
• Replace "TODO" with clear, actionable, and complete information about the changes and impacts.
• Ensure comprehensive documentation of the breaking changes and migration advice.

General Suggestions:

• Consider providing detailed migration guidance for the described breaking changes.

.changeset/warm-things-allow.md

Issue with: 'Implements Vite Environment API'

❌ Errors:
• The description lacks detail about the breaking change implications.
• Further information about user-facing aspects is missing.

💡 Suggestions:
• Expand the description to demonstrate the changes introduced by the "Vite Environment API" and any migration or usage guidance required.
• Elucidate user advantage or impact for this change.

Issue with: 'TODO: add more details'

❌ Errors:
• The inclusion of "TODO" signifies incomplete change details.
• Guidelines prohibit the use of placeholders in descriptions.

💡 Suggestions:
• Ensure the short description is appropriately finalized, presenting thorough and complete change details.
• Replace "TODO" with necessary complete content pertaining to the modification.

General Suggestions:

• Ensure descriptions for breaking changes adhere to guidelines by providing detailed user-facing implications.
• Remove placeholder text and ensure full details are presented.

---

📖 See Astro's changeset guide for details.