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

xmlchars

v2.2.0

Published

Utilities for determining if characters belong to character classes defined by the XML specs.

Downloads

84,427,299

Readme

Utilities for determining whether characters belong to character classes defined by the XML specs.

Organization

It used to be that the library was contained in a single file and you could just import/require/what-have-you the xmlchars module. However, that setup did not work well for people who cared about code optimization. Importing xmlchars meant importing all of the library and because of the way the code was generated there was no way to shake the resulting code tree.

Different modules cover different standards. At the time this documentation was last updated, we had:

  • xmlchars/xml/1.0/ed5 which covers XML 1.0 edition 5.
  • xmlchars/xml/1.0/ed4 which covers XML 1.0 edition 4.
  • xmlchars/xml/1.1/ed2 which covers XML 1.0 edition 2.
  • xmlchars/xmlns/1.0/ed3 which covers XML Namespaces 1.0 edition 3.

Features

The "things" each module contains can be categorized as follows:

  1. "Fragments": these are parts and pieces of regular expressions that correspond to the productions defined in the standard that the module covers. You'd use these to build regular expressions.

  2. Regular expressions that correspond to the productions defined in the standard that the module covers.

  3. Lists: these are arrays of characters that correspond to the productions.

  4. Functions that test code points to verify whether they fit a production.