npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

react-render-json

v1.0.5

Published

Render your API's JSON payloads using React!

Downloads

13

Readme

react-render-json

JSON is great — for computers! But we humans need something a bit more expressive. Why create a JSON object, when you can create an <Order />? Why should your API layer need to understand the JSON output format? Why use a different framework on the client to the server, just because they're totally different environments and honestly it's kind of weird they both run on Javascript at all???

Why write

{
	"orderId": 123,
	"customer": {
		"customerId": 456,
		"name": "Andrew"
	},
	"sku": {
		"skuId": 789
	},
	"shippingAddress": {
		// ...
	}
}

when you could write

	<Order
		id="123",
		customer={ <Customer id="456" name="Andrew" /> }
		sku={ <Sku id="789" /> }
		shippingAddress={ <Address { ...addressProps } /> }
	/>

???

Use react-render-json to define a whole rich model layer as React components, then render them directly to JSON! It's Enterprisey!

Installation

npm install --save react-render-json

A simple example

The simplest way of using this library is to just build your JSON objects directly:

import React from 'react';
import ReactJSON from 'react-render-json';

const payload = (
	<ReactJSON.Object
		id="object-id"
		entries={
			<ReactJSON.Array>
				<ReactJSON.Literal value={ 1 } />
				<ReactJSON.Literal value={ 2 } />
				<ReactJSON.Literal value={ 3 } />
			</ReactJSON.Array>
		}
	/>
);

res.body = ReactJSON.renderObject(payload);

This renders:

{
	"id": "object-id",
	"entries": [ 1, 2, 3 ]
}

A more complex example

The real power of react-render-json is in defining your own rich data model types in exactly the same way as you'd define any other React component:

import React from 'react';
import ReactJSON from 'react-render-json';

function Counter() {
	const { start, stop } = this.props,
		children = [];
	for (let i = start; i <= stop; i++) {
		children.push(
			<ReactJSON.Literal value={ i } key={ i } />
		);
	}
	return <ReactJSON.Array>
		{ children }
	</ReactJSON.Array>;
}

const payload = (
	<ReactJSON.Object
		id="object-id"
		entries={
			<Counter start={ 1 } stop={ 3 } />
		}
	/>
);

res.body = ReactJSON.renderObject(payload);

This emits the same JSON as the simple example, but with much less code! You can also use class-based React components!

There's an even more complex example in the example folder.