Skip to content

Conversation

@florian-lefebvre
Copy link
Member

@florian-lefebvre florian-lefebvre commented Nov 20, 2025

Changes

Testing

Updated, should pass

Docs

Changeset + withastro/docs#12745

@florian-lefebvre florian-lefebvre added this to the v6.0.0 milestone Nov 20, 2025
@florian-lefebvre florian-lefebvre self-assigned this Nov 20, 2025
@changeset-bot
Copy link

changeset-bot bot commented Nov 20, 2025

🦋 Changeset detected

Latest commit: d0e5e2b

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

@github-actions github-actions bot added pkg: astro Related to the core `astro` package (scope) docs pr labels Nov 20, 2025
@florian-lefebvre florian-lefebvre linked an issue Nov 20, 2025 that may be closed by this pull request
Copy link
Member

@Fryuni Fryuni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lovely! Thanks Florian!

Copy link
Member

@ematipico ematipico left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome

Copy link
Member

@sarah11918 sarah11918 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple of things to note!

This is a "top-level" config option, so the JSDoc needs to be added up in that section (see the docs PR, I'm suggesting after scopedStyleStrategy, but those are just arbitrarily listed by how "popular" we think the options are. It can go anywhere in that list. (In its current location, this would show up as an env configuration option.)

I know you're reusing the error message, so you haven't added/updated anything. BUT now that we have this config option, I think the error message (https://docs.astro.build/en/reference/errors/prerender-route-conflict/) could probably be updated to show more helpful links:

  • the link directly to route priority (probably more helpful than either of the existing links to getStaticPaths() or params?)
  • this new config option so that you can configure whether or not to see this message, maybe? (It can be a helpful reminder if someone sets error, then gets annoyed and wants to silence it, if the link to the config option is directly in the error message I think?) What do you think?

Copy link
Member

@sarah11918 sarah11918 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I updated all the suggestions to warn instead of warnING, in case that's helpful!

Copy link
Member

@sarah11918 sarah11918 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🚀

@florian-lefebvre florian-lefebvre merged commit 170f64e into next Nov 21, 2025
22 checks passed
@florian-lefebvre florian-lefebvre deleted the feat/stabilize-fail-on-prerender-conflict branch November 21, 2025 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs pr pkg: astro Related to the core `astro` package (scope)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stabilize experimental.failOnPrerenderConflict

5 participants