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

usfm2json

v0.0.23

Published

Yet another USFM to JSON parser

Downloads

7

Readme

usfm2json

Yet another usfm to json parser. Meant to render UnfoldingWord texts to json for use in OpenBible.

Uses a Pratt parser because my long regex was getting way too jank. No dependencies.

AST

All we need in our AST is what we will have in our HTML.

These ASTs will take bandwidth. I'm not going to deliver something to the user that they don't need to render the text on their screen.

AST chapters: [ [ {t: 's5', v: 'blah blah'}, {t: 'p', v: [ {t: 'v', n: 1, v: 'You have head that'} {t: 'w', v: 'Bob said, "'}, {t: 'q', v: 'ABCDEFG'}, {t: 'w', v: '," and then he was happy.'}, ]} ] ]

tags to make HTML

s# => headings c => nothing p => paragraph v => span {num} {text} w => fragment q => italic