fix: crawl hrefs that start with config.prerender.origin
#12277
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.
Closes #12271
Until now the crawler would not recoginze links that start with the value of
config.prerender.origin
as internal links & would not crawl them. This PR fixes that.For example: A link
<a href="https://my-site/base/some-page"
would not be crawled, even ifprerender.origin
was set tohttps://my-site
insvelte.config.js
.This is important since
<link rel="alternate"
requires links to be absolute URIs that include the protocol, so until now it was impossible for the crawler to discover pages that were linked to in valid<link rel="alternate"
links.Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpm changeset
and following the prompts. Changesets that add features should beminor
and those that fix bugs should bepatch
. Please prefix changeset messages withfeat:
,fix:
, orchore:
.Edits