fix(astro): restore Astro.site in getStaticPaths() #14576
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #14575
Summary
Restores
Astro.site
availability ingetStaticPaths()
by adding back theastroGlobalArgs
compiler option that was removed in PR #14405.Bug
In v5.13.10,
Astro.site
becameundefined
when accessed insidegetStaticPaths()
, even when properly configured inastro.config.mjs
.Root Cause
PR #14405 removed the
astroGlobalArgs
parameter from the compiler options. This parameter passes the site configuration to the Astro compiler, which injects it into the compiled component, makingAstro.site
available in the frontmatter code (includinggetStaticPaths()
).Fix
This PR restores the single line that was removed:
Testing
Verified that
Astro.site
is now correctly available ingetStaticPaths()
as a URL object with the configured site value.Before (v5.13.10)
Astro.site
ingetStaticPaths()
:undefined
After (with this fix)
Astro.site
ingetStaticPaths()
:URL { href: 'https://example.com/', ... }