Skip to content

fix: add empty integrations array to Astro config#16528

Closed
rodrigosdev wants to merge 1 commit into
withastro:mainfrom
rodrigosdev:fix/add-integrations-to-astro-config-on-basic
Closed

fix: add empty integrations array to Astro config#16528
rodrigosdev wants to merge 1 commit into
withastro:mainfrom
rodrigosdev:fix/add-integrations-to-astro-config-on-basic

Conversation

@rodrigosdev

Copy link
Copy Markdown
Contributor

Changes

  • Adds an explicit empty integrations array to the examples/basics Astro config.
  • Keeps the basic example aligned with config shape that includes integrations.

No changeset added because this only updates an example config and does not affect package behavior.

Testing

Not run. This is a config-only example update with no runtime behavior change.

Docs

No docs update needed. This only changes an example config.

fixes #16526

@changeset-bot

changeset-bot Bot commented Apr 30, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: c19e87f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions github-actions Bot added the pkg: example Related to an example package (scope) label Apr 30, 2026
@rururux

rururux commented Apr 30, 2026

Copy link
Copy Markdown
Member

Hi! Thank you for opening this pull request.

However, as Houston bot commented on the issue, I believe this is actually a bug where the integrations parameter is being treated as required when it shouldn't be.
Could you open a new pull request that fixes the root cause of why it's being treated as required, rather than going with the current approach?

Thank you!

@rodrigosdev

Copy link
Copy Markdown
Contributor Author

Hi! Thank you for opening this pull request.

However, as Houston bot commented on the issue, I believe this is actually a bug where the integrations parameter is being treated as required when it shouldn't be. Could you open a new pull request that fixes the root cause of why it's being treated as required, rather than going with the current approach?

Thank you!

I Agree, I will close this one and open a fix for the root cause. This was made before the Huston bot analysis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pkg: example Related to an example package (scope)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dev Server won't load on the basic template

2 participants