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 🙏

© 2026 – Pkg Stats / Ryan Hefner

editor-to-jsx

v1.0.3

Published

Editor.js to JSX element conversion module, very lightweight, very fast, very clean.

Readme

editor-to-jsx

Dependencies

  • React... THATS IT!

Purpose

This library serves to be a lightweight utiltiy to parse data from Editor.js, it was developed as the need arose for the ability to utilize the ease of use of Editor.js, alongside React, or the ever-increasing benefits of NextJS

Clean data output from Editor.js comes in JSON form, with an exact formatting of:

{
    "time":1618024997507,
    "blocks":[
      {
        "type":"header",
        "data":{
          "text":"This is test data for editor-to-jsx",
          "level":1
        }
      },
      {
        "type":"embed",
        "data":{
          "service":"youtube",
          "source":"https://www.youtube.com/watch?v=VYUa5MxREkk",
          "embed":"https://www.youtube.com/embed/VYUa5MxREkk",
          "width":580,
          "height":320,
          "caption":"Caption for Embed<br>"
        }
      },
      {
        "type":"checklist",
        "data":{
          "items":[
            {
              "text":"Checklist Item 1 (checked)",
              "checked":true
            },
            {
              "text":"Checklist Item 2",
              "checked":false
            },
            {
              "text":"Checklist Item 3",
              "checked":false
            }
          ]
        }
      }   
    ],
    "version":"2.20.1"
  }

After parsing, the end result looks identical to the editor, as seen below: editor-to-jsx

Thank you for using this library, pull requests are welcome, and I hope this helps you in your ventures

  • Toby Hagan

Usage

There are currently two functions available from exitor-to-jsx:

  • function parseBlock
  • component <Block />
-Use With NextJS

In this example, data is fetched with the fetch API then passed as props to allow for server side rendering. the data passed to parseBlock() should be only one block from the entire article's array or blocks, as seen acomplished in the map() function below. The parseBlocks() function will return an array of props, which should then be passed on to the <Block props={} /> component as props, with a key of props.key

import { useContext,} from "react";
import { PostContext } from "../context/PostContext";
import {parseBlock, Block} from 'editor-to-jsx'
export default function Home({data}) {
  return (
    <div>
      {data.blocks&&(
        data.blocks.map(block=>{
          const props = parseBlock(block)
          return <Block key={props.key} props={props} />
        })
      )}
    </div>
  )
}
export const getServerSideProps = async () => {
  const res = await fetch('<your-endpoint-here>')

  const data = await res.json()
  return {
    props: {
      data,
    },
  }
}
-Use with React
import {useEffect, useState} from 'react'
import {parseBlock, Block} from 'editor-to-jsx'
function App() {
    const [data, setData] = useState(null)
    const getData = async() => {
        const res = await fetch('<your-endpoint-here>')
        const initialData = await res.json()
        setData(initialData)
    }
    
    useState(()=>{
        getData()
    },[])

  return (
    <div>
      <header>
      {data.blocks&&(
        data.blocks.map(block=>{
          const props = parseBlock(block)
          return <Block key={props.key} props={props} />
        })
      )}
      </header>
    </div>
  );
}

export default App;