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

htmx-persist-fields

v1.0.3

Published

Htmx extension to persist fields to different storages

Downloads

57

Readme

htmx-persist-fields

Htmx extension to persist fields to different storages.

Status

Experimental. I've used this a little, but not much. Any feedback and suggestions are welcome!

Motivation

Decouples state persistence from state handling.

Application can either synchronize its state to the DOM or use the DOM as the master of state directly. This also enables to use CSS for directly interacting with state, for example to show/hide elements based on some state.

Available storage options

  1. localStorage
  2. sessionStorage
  3. cookie
  4. URL fragment
  5. URL query string
  6. http

Install

<script src="https://unpkg.com/htmx-persist-fields/dist/persist-fields.js"></script>

Usage

<body hx-ext="persist-fields">
  <div persist-fields-local="mystuff">
    <input name="param" value="val" />
  </div>
</body>

Specify the store with attribute:

  1. persist-fields-local
    • suitable for persistent storage across sessions
    • value is store key
  2. persist-fields-session
    • suitable for temporary storage for the duration of the session, and when the state is wanted to stay only client-side
    • value is store key
  3. persist-fields-cookie
    • suitable for temporary storage for the duration of the session, and when the state might be used server-side
    • value is cookie options, e.g. path=/;max-age=31536000
  4. persist-fields-fragment
    • suitable for state shared with other users using ordinary links, and when the state is wanted to stay only client-side
    • value is empty string or
    • value is constant indexed. Input values will be stored in the fragment as just values (without keys) separated by #
  5. persist-fields-query
    • suitable for state shared with other users using ordinary links, and when the state might be used server-side
    • value is empty string or
    • value is constant indexed. Input values will be stored in the query as just values (without keys) separated by &
  6. persist-fields-http
    • suitable for persistent storage across different browsers or users
    • value is the URL to GET the data from and PUT the data to.

All following descendants will be persisted, unless they are descendants of hx-ext="ignore:persist-fields".

  1. form fields having name attribute and
  2. any elements having persist-fields-name attribute (e.g. a contenteditable div)

Readonly or disabled (or descendants of disabled fieldset) fields are initialized from the store, but their values/changes aren't persisted.

Only values that differ from their default value (if specified in the markup) are persisted, unless the field is marked required in which case the value is always peristed.

For indexed storage, multiple inputs with the same name are concatenated when persisted, and matched back to the correct input based on type/pattern/length/readonly-value when initialized. This can be used for example to build a nice looking "API" of the URL fragment.

To clear the persisted fields and restore inputs to their default values, dispatch the htmx:persistFieldsClear event:

<button onclick="htmx.trigger(this, 'htmx:persistFieldsClear')">restore defaults</button>