react-data-debugger

A developer debugging tool to view js object changes over time.
This tool is intended for using while developing, and not for production code.

Built with ballerina

Goals and contribution

Debugging react issues, particularly with state changes and excess rendering often requires examining data structures under change.

Using console logs makes it hard and time consuming to detect changes in the data. Rendering the data straight on the page makes it hard to catch real time changes.

This widget allows you to render and page through changes to an js object without interfering with your code or layout.

It's main goals are to be easy to use with minimal set up and to provide a basic set of useful features.

Quick start

$3

npm

``npm i react-data-debugger --save-dev`

yarn

`yarn add react-data-debugger --dev`

$3

`import { Debugger } from "react-data-debugger";`

$3

`
export const BuggyComponent = (props) =>
{
const [myObject, setMyObject] = useState({});

Debugger({jsObject: myObject, open: true, label: "1"})

return (
<>




My component


....


)
}
`

Options

The debugger accepts some options for convenience:

| prop | type | Function |
| ---- | ---- | --------- |
| label | string | renders a name for the debugger, useful when using multiple debuggers
| open | boolean | The debugger is initially open
| lightMode | boolean | The debugger is initially in lightmode
| noReplaceUndefined | boolean | When true, does not replace undefined values with null in the displayed output, reflecting the actual js object.

Note: The options are not global and must be specified per debugger

Additional Info

You can use the Debugger as man times as desired within a component to debug different data.

It can be handy to call the debugger with the same data to examine differences in steps over time (diffing).

Each debugger is rendered in its own shadow dom, avoiding css clashes.

The javascript object passed in is rendered using JSON.stringify, according the JSON spec, undefined values are stripped out. This may be undesirable for debugging, so by default undefined values are replaced with null. This helps tracking a value over time. This behaviour can be turned off by setting the `noReplaceUndefined`` prop.