Browser developer tools

Nock’s workers can investigate a page using developer tools in Nock’s own browser. Ask for a concrete result: “find the console error on this page,” “tell me its font sizes and colors,” or “record the traffic while you open the settings screen.”

Choose the investigation

Ask for	What the worker can inspect
Network recording	Request addresses, methods, statuses, types, sizes, timings, and sanitized headers; bounded text bodies when requested.
Page assets	Scripts, styles, pictures, fonts, media, metadata, CSS variables, and links loaded by the page.
Console	Messages, warnings, and errors captured while the tab loads and runs.
Computed styles	The final colors, fonts, spacing, layout, and effects for matching elements.
Readable script source	Published source maps, or an unpacked and formatted bundle when a source map is absent.

Nock hands the investigation to a worker. You can continue the conversation while it inspects its tab, then open the worker result and files.

Record a reproducible problem

Tell the worker which page and steps matter. Start recording before reloading or opening the page, then reproduce the action. A recording cannot recover requests that finished before recording began.

For example:

Open my local preview, start recording, reload, click Save, and explain the failed request. Save the recording in the project.

The bounded buffers keep up to 1,000 requests and 1,000 console lines per tab. Third-party frame traffic, background service-worker requests, and live WebSocket message contents are outside the recording; a connection address may still appear.

Keep results in your project

Saved recordings and reconstructed scripts go inside your project. A script inspection can include the original downloaded script, a source-map result or readable modules, and a manifest linking the outputs to the page’s assets. A reconstructed bundle is an aid to understanding, not a guarantee of the original developers’ source structure.

When no source map exists, the readable-bundle tool may need its one-time dependency download and a local Node.js runtime. The worker reports if that preparation cannot run. It does not execute a downloaded script simply to make it readable.

Sign-ins and data

Workers use Nock’s browser profile according to your browser settings. The developer tools remove recognized credentials, cookies, sign-in headers, and token fields from captured data before exposing it to the worker. Ordinary page content can still contain private information; review a recording before sharing it.

The page and its assets load from their websites. Material the worker reads can be sent to its model as context. Use the tools to inspect your own work or study behavior you are allowed to inspect, and preserve applicable licenses when reusing code or assets.

See Nock’s browser, Projects, and Coding permissions.