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

hx-dataset-include

v0.0.6

Published

Brutally simple htmx extension to make data-* html attributes participate in the requests

Downloads

3

Readme

hx-dataset-include

npm MIT

Brutally simple htmx extension to make data-* html attributes participate in the requests

How to use

Just import the extension tag in your html:

<script type="text/javascript" src="https://unpkg.com/[email protected]/dist/htmx.min.js"></script>
<script type="text/javascript" src="https://unpkg.com/[email protected]/lib/hx-dataset-include.js"></script>

Then enable it in the element doing the request:

<!-- example: PUT task information when a custom event from alpinejs triggers 
 the request -->
<article class="message task"
         hx-ext="hx-dataset-include"
         id="task1"
         data-task="1"
         data-status="DOING"
         hx-put="/task/1"
         hx-trigger="put-task"
         draggable="true"
         @dragstart="e => e.dataTransfer.setData('text/plain', $el.id)"
         @update-status.window="e => {
            if(e.detail.taskEl == $el) { // needed to filter real target
                $el.dataset.status=e.detail.lane.dataset.status
                $dispatch('put-task', $el.dataset)
            }
         }">
  <!-- rest of the markup -->

Motivation

In hypermedia systems, the markup IS the application state. It was true for the html form element for ages and motivated the approach of include everything that contains a value attribute in the htmx requests.

But sometimes there is no form, or it feels illegal to use a custom value attribute.

The data-* attributes are perfectly legal and well documented. Also you can have as many of them as you want in your html tag!

Further reading

  • Read the always good, enlightening, HATEOAS Essay.
  • See other extensions for htmx here.
  • Checkout Alpinejs, the extra spice for your hypermedia app.