NativeScope module 03 · available now

A log is a clue. Timeline shows the story.

Capture JavaScript console output from boot, inspect the values behind each line and connect the moment that matters to every request and storage write around it. Fully local, inside the same Studio.

Add LogsRead the docs
  • JavaScript console
  • Captures from boot
  • Local + bounded
Logs · NativeScope Studiolive
NativeScope Timeline showing a highlighted log error with surrounding requests and storage changes

console.*passthrough capture, no new logger

1 lineto enable the whole module

×N + droppedhonest protection from bursts

0 cloudlocal service, local Studio

NativeScope Timeline placing logs, a request and storage activity before and after the selected error

The reason Logs matters

One moment. Every signal around it.

A console line rarely explains itself. Open Timeline from a log, an error, a failed request or a Mark and NativeScope aligns the three sources on one clock. The selected moment stays unmistakable; the context before and after can expand only when you need it.

  • Choose ±5s, ±30s, ±2min or an event count.
  • Toggle Logs, Network and Storage independently.
  • Keep a Mark as the start of a focused investigation.
Learn how Timeline works

Read what the app actually emitted

Keep the stream fast. Keep the evidence intact.

The list stays chronological and virtualized for long sessions. Filter by level or namespace, search the message and its data, expand any line and open the complete object in the same viewer you already know from Storage.

  1. 01
    Find the signalSearch, level counts, namespaces and repeat grouping keep noise out.
  2. 02
    Open the evidenceObjects, arrays and stacks remain inspectable, searchable and copyable.
  3. 03
    Move to the causeJump from the exact line into its scoped Timeline.
Learn the Logs workflow
NativeScope Logs showing a selected structured object and its JSON detail viewer

Built for real development streams

Less console archaeology. More useful decisions.

Logs keeps the ordinary console workflow intact, then adds the controls that make a long, noisy session understandable when something goes wrong.

Find the useful line

Search messages, namespaces, stacks and structured arguments without losing the surrounding stream.

Learn more

Inspect the real value

Objects, arrays and errors open in the same visual JSON workspace used by Storage — not a flattened terminal preview.

Learn more

Take the exact evidence

Copy a log or its JSON payload into a bug report, issue or investigation without reconstructing it by hand.

Learn more

Survive noisy sessions

Repeated lines become ×N, bursts respect a per-second ceiling and dropped entries stay visible instead of disappearing silently.

Learn more

Mark the moment

Drop a marker before an action, keep the earlier stream out of the way and focus on everything that follows.

Learn more

See the whole story

Open Timeline from a log, error or request and place Logs, Network and Storage on one chronological axis.

Learn more

The whole integration

One line turns the module on.

Start with the defaults. When a project needs a narrower stream, configure levels, payload bounds, batching, the startup buffer or ignored namespace patterns in the same root config file.

See the configuration
nativescope.config.ts
import { defineNativeScopeConfig } from
  "react-native-nativescope/app"

export default defineNativeScopeConfig({
  modules: {
    logs: true,
  },
})
Capture starts before the Studio connects.

Useful boundaries

Detailed when you ask. Bounded when you do not.

JavaScript scope. Logs captures the JavaScript console and global uncaught errors and rejections. It does not replace native device logs or Metro’s terminal.

Finite by design. Startup buffering, entry limits, bounded values, repeated-line merging and a per-second ceiling protect the app from turning its own debug stream into a performance problem.

Local is not automatic redaction. Captured values stay in the local development path, but console arguments are still sensitive. Do not log secrets; Logs does not silently redact them for you.

Logs is live

Stop reading the line in isolation.

Enable LogsExplore Timeline