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

input-proxy

v1.0.0

Published

Removes some of the hassle when storing JSON in an input.

Downloads

1

Readme

Input Proxy

Store JSON in an HTMLInputElement with less hassle

Reason

Forgetting to restringify your JSON into the input? Tired of writing the same function to unparse the JSON just for one value?

I sure did! So I wrapped my HTMLInputElement in a Proxy, and wrote some get and set methods to deal with just that.

Benefits

Pass in an HTMLInputElement, and then the value becomes a JSON object that you can access just be requesting the key.

Example

import { IP } from '../input-proxy.js';

const input = document.getElementById('StoresJSON');
const wrappedInput = IP(input);

wrappedInput.name = 'John'; //

wrappedInput.name; // 'John'

// Access the input values like so
input.value; // '{ "name": "John" }'
// or
wrappedInput.__value; // '{ "name": "John" }'

// If a key hasn't been set or is deleted,
// InputProxy returns null
delete wrappedInput.name;

wrappedInput.name; // null

WARNING

To prevent issues with JSON.stringify, on creation InputProxy sets the value of the element passed in to be '{}'.