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

express-htmx-components

v1.2.9

Published

Simple htmx component server for Express

Downloads

37

Readme

Express </> HTMX Components

Experimental Express powered HTMX component framework

What is this?

This is a very simple library to make developing HTMX based apps as pleasing as possible in Express. You should be able to just focus on writing an HTMX response (it's basically how HTMX works) and use the same code to compose components in a page.

To achieve this components are both web pages (they have a URL) and functions (they return HTML). This basically allow HTMX to just work™ - the component can update itself by making a request to its own URL.

What is HTMX

If you don't know HTMX I strongly encourage you to check it out: https://htmx.org/.

HTMX is basically a re-thinking of AJAX. Instead of returning JSON and using javascript to insert the data into the document HTMX returns HTML as data.

With HTMX you can basically create reactive web apps without writing any javascript.

OK, so what exactly is a COMPONENT?

Here's an example of a simple counter component:

const counter = component.get("/counter", ({ id, count }) => {
  return html`
    <div id="count-${id}">
        <h3>${count}</h3>
        <button hx-get="/counter/incr?id=${id}&count=${count}"
          hx-target="#count-${id}"
          hx-swap="outerHTML"
        >
          +1
        </button>
    </div>
  `;
});

const incr = component.get("/counter/incr", ({ id, count }) => {
  let n = count;
  n++;
  return counter.html({ id, count: n });
});

module.exports = { counter, incr };

Each component exports an object with two properties:

  • html - A function that returns the rendered component
  • route - An Express route that serves the rendered component

All query params are converted to arguments/props passed to the component. This is what makes the component usable both as an endpoint and a function.

Docs