Repository navigation
docs: add a soft navigations integration page - #357
Merged
Merged
Conversation
Shows how to use @push-based/lighthouse-soft-navigation in a flow file, and links to its docs for how soft navigation steps are measured.
❗❗❗ report generated by this PR ❗❗❗☕ Order Coffee ☕Date/Time: 2026-11-13 19:47
|
☕ Order Coffee ☕Date/Time: 2026-11-13 19:48
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 356
Adds Integrations → Soft navigations, which covers how to use
@push-based/lighthouse-soft-navigationwith user-flow:.user-flowrc.json--dryRundoesn't work yet (--dryRun fails for navigate callbacks and startNavigation/endNavigation #355)How soft navigation steps are recognised and measured, throttling and limits stay in the lighthouse-soft-navigation docs, and the page links to them. The complete-configs example in Lighthouse configuration now links to the new page.
The production docs build prerenders the new route. I checked the page in a screenshot.