--- schema_version: 1 route: /t/lighthouse.md tool: "lighthouse" --- # sincecutoff.com /t/lighthouse — Lighthouse - name: Lighthouse - kind: cli - children: none - homepage: Changes to the tools coding agents drive, since a model's training cutoff, each linked to its first-party source. Check installed versions and limitations before acting; a cutoff date does not establish what a model knows. Original editorial content: [Apache 2.0](https://sincecutoff.com/v1/data-license.txt), by [0xPatrick](https://0xpatrick.dev). Preserve applicable license and [NOTICE](https://sincecutoff.com/notice.txt) attribution when redistributing. Third-party source text and examples retain their own rights. [License scope and attribution](https://sincecutoff.com/v1/license.json). To stay current, read the changes feed: [`/v1/changes.md?tool=lighthouse`](https://sincecutoff.com/v1/changes.md?tool=lighthouse) (or `.json`), adding `since=YYYY-MM-DD` for your training cutoff. Entries for registered children are included; the registry itself is `/v1/tools.json`. How to page and save your place: [llms.txt](https://sincecutoff.com/llms.txt). ### Lighthouse user flows can dispose of pending navigation waits (2026-09-18) - slug: lighthouse-user-flows-can-dispose-of-pending-navigation-waits-97f8d98de389 - score: 0.93 How to use it: If a Lighthouse user-flow navigation fails, call `flow.dispose()` in the catch path to cancel pending navigations and clean up wait conditions. Closing the Puppeteer page also disposes of those conditions automatically, according to the v13.5.0 release note. Examples: ``` try { await flow.startNavigation(); await page.goto('https://invalid-url.dev/'); await flow.endNavigation(); } catch (error) { flow.dispose(); console.error("Navigation failed:", error); } ``` - why_it_matters: Handle a failed navigation in a Lighthouse user flow without waiting for navigation conditions to time out. - before: After a failed navigation, programmatic usage had to await for wait conditions to throw timeout errors. - sources: , , - gotchas: "Version: v13.5.0"; "flow.startNavigation() (required): Starts a navigation step; surround the action that triggers navigation with `startNavigation()` and `endNavigation()`."; "page.goto(url) (required): Puppeteer navigation action; the docs' failure example uses `https://invalid-url.dev/`."; "flow.endNavigation() (required): Ends the navigation step after the triggering action."; "flow.dispose() (required): Cancels navigations and cleans up wait conditions; call it in the failure handler."; "Prerequisite: User flows use the Lighthouse Node API with Puppeteer." ### Lighthouse TypeScript consumers can import public types from lighthouse/types.js (2026-06-09) - slug: lighthouse-typescript-consumers-can-import-public-types-from-lighthouse-types-js-f99a2efe8a20 - score: 0.98 How to use it: When TypeScript code consuming Lighthouse needs the LH Audit namespace type, import it from the public type-only entrypoint `lighthouse/types.js`. Examples: ``` import type { Audit } from 'lighthouse/types.js'; ``` - why_it_matters: Import Lighthouse Audit types while implementing TypeScript code that consumes Lighthouse. - before: Import types such as `LH.Audit` from the nested `lighthouse/types/lh.js` path. - sources: , , - gotchas: "Version: v13.4.0"; "Audit (required): Type namespace re-exported from `types/lh.js` by the public type-only entrypoint." ### Lighthouse adds a default WebDX Baseline compatibility audit (2026-04-07) - slug: lighthouse-adds-a-default-webdx-baseline-compatibility-audit-2f69cbf0b4a8 - score: 0.97 How to use it: When auditing a page with Lighthouse v13.1.0, use the default configuration to run the Baseline audit. Review the report’s feature status icons and version descriptions; the audit reads WebDX feature usage trace events. Examples: ``` lighthouse ``` - why_it_matters: Check a page’s WebDX Baseline compatibility while auditing its behavior in Lighthouse. - sources: , , , , , , , - gotchas: "Version: v13.1.0"; " (required): Page URL to audit."