Narzędzia

`tooling/console-clean`

Pages log no errors and use no deprecated browser APIs, as seen in the console on load and in the main flows.

drobnaw przeglądarcefe-lighthouse

Dlaczego

Console errors are failed requests, uncaught exceptions and broken features that someone has already hit. Deprecated APIs (for example unload handlers, synchronous XHR, document.domain) stop working in a later browser release, usually without notice to the site owner.

Poprawka

Open the console on each changed page and fix every error at its cause (a missing file, a null reference, a CSP block), not by catching and hiding it. Replace each deprecated API the Issues panel lists. Errors from extensions do not count; errors from your third parties do.

Przykłady

// bad: hides the error and the broken feature
try { initMap() } catch {}
// good: fix the cause, report what remains
if (mapElement) initMap(mapElement)

Źródła

Fakty

Identyfikator: tooling/console-clean
Waga: drobna
Sprawdzanie: w przeglądarce wymaga wyrenderowanej strony: audit --url
Dotyczy plików: page
Ten sam problem w: Lighthouse errors-in-console, Lighthouse deprecations
Uczy jej skill: fe-lighthouse Lighthouse and PageSpeed
Od wersji: 0.1.0

Plik reguły na GitHubie

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain tooling/console-clean