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

jasponyx

v0.4.3

Published

The opinionated JSX pretty printer

Downloads

7

Readme

Jasponyx

It's an opinionated JSX pretty printer for the command line.

Usage:

Context:

import React, { Component } from 'react'
import ReactDOM from 'react-dom/server'
import pp from 'jasponyx'

class CompOne extends Component {
  moreStuff() {
    return React.Children.map(this.props.children, (_, i) =>
      <div>Count me off, Juliet {i}</div>)
  }

  render() {
    return (
      <div>
        {this.moreStuff()}
        And they've got spices!
        <CompTwo
          props="aren't"
          very="convenient"
          to="think about"
          andANumber={5}
        />
        {this.props.children}
      </div>
    )
  }
}

function CompTwo({ props, very, andANumber }) {
  return (
    <div>
      {props}: {very}, {andANumber}
    </div>
  )
}

const tree = (
  <div className="quarks probably">
    <CompOne
      crazy={{
        long: 'props',
        are: 'in',
        abundance: [
          'these days you silly goose'
        ]
      }}
    >
      Naked words should work too
      <span>Hymns and mantras and stuff</span>
    </CompOne>
    <div/>
  </div>
)

For some orientation, this is how React renders it.

console.log(ReactDOM.renderToStaticMarkup(tree))

Minified html markup as rendered by ReactDOM

Gross, right?

console.log(pp(tree))

Pretty output from jasponyx with nothing turned off

console.log(pp(tree, { props: false }))

Pretty output from jasponyx with props turned off

console.log(pp(tree, { native: false }))

Pretty output from jasponyx with only composite nodes and text (no native)

console.log(pp(tree, { native: false, text: false })

Pretty output from jasponyx with only compiste nodes (no native or text)

console.log(pp(tree, { nativeProps: false }))

Pretty output from jasponyx without props on the native nodes

console.log(pp(tree, { composite: false }))

Pretty output from jasponyx without composite nodes (only native and text)

Note the similarities to the output of ReactDOM.renderToStaticMarkup

console.log(pp(tree, { compositeProps: false }))

Pretty output from jasponyx without props on the composite nodes

FAQ that no one has never asked

Q. Why "jasponyx"?

A: curl -L https://github.com/dwyl/english-words/blob/master/words.txt?raw=true | rg j.*s.*x

Q: But what if I want some other kind of styling or opinion?

A: First of all, wow! Thanks for using our library! Second of all, make an issue. Or better yet, make a PR. =) We built this for internal debugging use, and were pretty surprised it didn't already exist in some form or another. There's jsx-to-string and a couple others, but those only go one layer deep. We basically wanted the React Devtools output in the console.

Q: What about lifecycle hooks?

A: Not necessary for our usecase, and we don't even know how you'd render that kind of thing. So this only does the initial load. with the composite option set to false, the output should basically be a colorized version of react-dom/server's .renderToStaticMarkup's output.