JavaScript & Frontend · page 7

Combine supplied dependency checks into a service health summary.

Create a dashboard plan from service metrics, alerts, dependencies, and operational goals.

Identify export and side-effect patterns that may prevent unused code elimination.

Compare package side-effect declarations with supplied module behavior metadata.

Compare bundle manifests to identify repeated dependencies across entry points.

Suggest candidate chunk boundaries using dependency relationships and entry points.

Verify that generated JavaScript bundles have matching source map references.

Find missing or incorrectly referenced source files in supplied source maps.

Compare entry points, chunks, hashes, and file sizes across builds.

Inventory language and browser APIs used in supplied source files.

Flag syntax and APIs that may conflict with a specified runtime target.

Find potentially confusing mixtures of logical OR and nullish coalescing.

Identify operations that mix BigInt and Number values incompatibly.

Find date parsing patterns that may vary by format or runtime environment.

Find asynchronous workflows without a clear cancellation mechanism.

Compare intended timer intervals with observed callback timestamps.

Suggest delegation boundaries based on repeated elements and event bubbling.

Compare custom event names and payload structures across source files.

Analyze supplied DOM update patterns for repeated layout-affecting operations.

Compare queried selectors with supplied markup and identify unmatched references.

Find patterns that may retain references to removed DOM nodes.

Detect repeated layout reads and writes in the same execution path.

Test response handling for success, empty bodies, invalid JSON, and HTTP errors.

Generate test cases for abort signals and timed-out requests.