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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@sea-squad/eelement

v0.0.5

Published

build html using typescript

Readme

SeaSquad Eelement

Eelement

Build HTML using TypeScript.

Getting Started

Installation

npm install @sea-squad/eelement

Overview

  • Build html in the TypeScript language using tuples
  • Just remember: an opening bracket indicates a new html element
  • Tuple structure is automatically formatted to be readable and html-like using a standard code formatter
  • First tuple element is the html tag name, optionally the second tuple element is an object of attributes, remaining tuple elements will become children of the element
  • String children are html escaped to avoid cross-site scripting (XSS), with the exception of script and style html elements
  • Output is a spec-compliant html string properly accounting for void and non-void elements
  • TypeScript enforces that no children may be passed to void elements

Usage

import { render } from "@sea-squad/eelement";

const myComponent = render([
  "html",
  ["head", ["title", "Hello Page"], ["meta", { charset: "UTF-8" }]],
  [
    "body",
    { class: "container" },
    ["h1", "Hello, World!"],
    ["p", "This is a paragraph."],
  ],
]);

console.log(myComponent);

Result

<!DOCTYPE html>
<html>
  <head>
    <title>Hello Page</title>
    <meta charset="UTF-8">
  </head>
  <body class="container">
    <h1>Hello, World!</h1>
    <p>This is a paragraph</p>
  </body>
</html>

Use Cases

This will serve you well if you:

  • Want something JSX-like, without investing in JSX
  • Need Type safety by staying in TypeScript
  • Want something with more guard rails to write proper html than a string template literal
  • Need auto-escaping of user-defined strings
  • Need i18n (can just us a t function where needed)
  • Are taking a hypermedia approach (htmx, datastar, fixi.js, plain html, etc)
  • Are writing plain TypeScript web components

This will not be a good fit if you:

  • Need to send chunked html responses (produces the whole document string at once)

Development

To build the project, run the following command:

npm run build

This will compile the TypeScript files to JavaScript and output them to the dist directory.

Testing

To run the tests, use the following command:

npm test