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

markdownstream

v0.0.3

Published

Streaming markdown parser that allows round-tripping and patching

Downloads

14

Readme

MarkDownStream build status

Streaming markdown parser that will allows round-tripping and patching

WARNING: Only for parsing code blocks currently

Ever wanted to parse a markdown file, and just fix certain things? Like maybe extract all the code segments, or add numbering to the headers, or fix all the numberings of ordered lists?

Well, now you can.

...

Actually, right now you can't, because I'm still working on it.

What you can do right now:

  • Stream through a file
  • Capture all code blocks, both in raw and parsed form
  • Re-render code blocks, switch from fenced to unfenced
  • Automatically render code blocks as fenced if tags are given

What is planned

  • Detect and expose other chunk types (headers, lists, paragraphs, etc.)
  • Cleaner parsing