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

genhtml-js

v0.1.0

Published

pure Javascript HTML generation and templating

Downloads

11

Readme

genhtml-js

Description

  • Model
    • nodes
      • name: /^[a-zA-z]+$/
      • attributes
        • unique names
      • children: any number of nodes, comments, texts
    • text
      • value: /^([^&<>"']|&(lt|gt|amp|quot|apos);)*$/
    • attributes
      • name: /^[a-zA-z]+$/
      • value: /^"([^&<>"']|&(lt|gt|amp|quot|apos);)*"$/ escaping single-quote delimiting? question: what about empty or missing values?
    • comments
    • root
      • doctype: ?? any number of attribute names or strings?
      • children: any number of nodes, comments, texts
  • Serialization
    • significant whitespace
    • self-closing tags vs. open/close pairs

A laundry list of aspects (some may not be implemented)

  • model

    • elements
    • attributes
    • comments
    • root node
    • text nodes
    • schema: child nodes, attributes allowed
    • directives
      • <!doctype html>
    • processing instructions
    • cdata
    • document type declaration
  • serialization

    • escaping: structure of document must not be changeable through serialization loopholes
      • < -> &lt;
      • amp, gt, apos (same as #x27 -- hex ??), quot
      • what is "replacement text" and what does it have to do with double escaping?
    • empty elements -- <input /> versus open/close pairs: <a></a>
    • ?? sanitizing ??
  • syntax restrictions

    • elements
      • names: spec for both element & attribute names
      • wikipedia: tag names can't include any of -.0123456789!"#$%&'()*+,/;<=>?@[\]^{|}~`, or spaces
    • attributes
      • names
      • unique names within an element
    • comments
      • no escaping (according to wikipedia)
      • can't have -- inside a comment
  • (in)significant whitespace

    • pre vs p