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

high5

v1.0.0

Published

(eventually) spec-compliant html 5 parser

Downloads

86

Readme

#high5

(eventually) spec-compliant html5 parser

###Goals

My previous HTML parser, htmlparser2, reached a point where a clean cut was needed. high5 is this cut, even though it's based on htmlparser2 and will try to be backwards compatible (I even tried to preserve the git history, so all previous committers are still credited).

Some of the things that will be supported:

  • [x] doctypes were treated as processing instructions & not parsed at all.
  • [x] Several token types that were previously handled as processing instruction tokens are handled as (bogus) comments in the HTML5 spec.
  • [ ] The xmlMode option will still be available & conditionally switch these features on.
  • [ ] Add a document mode. (htmlparser2 is always in fragment mode, meaning that eg. the empty document ("") will result in an empty DOM.)
  • [ ] Implicit opening & closing tags. (htmlparser2 only checks the top element of the stack for the latter.)
  • [ ] Foster parenting (eg. <table><a>foo</a>… should be handled as <a>foo</a><table>…).
  • [ ] (Potentially) handle character encodings (?).

###State

  • Spec-compliant* tokenizer
  • Rudimentary tag-handling (still a long way to go, only marginally better than htmlparser2).

* The tokenizer takes several shortcuts, which greatly increase the speed of a JavaScript implementation, but disobay the spec implementation-wise. The output should be spec-compliant, though.