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

elementsproxy

v1.1.0

Published

Direct access to any HTMLElement with an ID.

Downloads

3

Readme

Elements Proxy

Direct access to any HTMLElement with an ID:

<div id="myId">Hi</div>

<script>
  import elementsProxy from 'https://unpkg.com/[email protected]';

  const elements = elementsProxy();
  elements.myId.textContent; // "Hi"
</script>

This function returns a Proxy object. When a property is accessed on that object, the Proxy takes the property name and uses getElementByIdI() to find an element with an id of the same name. It then caches the element on the returned object for direct and instant access.

Why?

Because document.all is unreliable and document.getElementById() gets messy:

// Create lots of references to all the elements you need
const a = document.getElementById('a');
const b = document.getElementById('b');
const c = document.getElementById('c');
const d = document.getElementById('d');
const e = document.getElementById('e');
const f = document.getElementById('f');
const g = document.getElementById('g');

// do stuff with them
if (x > y) {
  a.textConent = 'Hello world';
  a.hidden = false;
}

b.classList.toggle('flex-col');
c.addEventListener('click', callback);
// and so on...

// Or worse:
// Repeated use of the id string, wasted lookups, noisy code
if (x > y) {
  document.getElementById('a').textConent = 'Hello world';
  document.getElementById('a').hidden = false;
}

document.getElementById('b').classList.toggle('flex-col');
document.getElementById('c').addEventListener('click', callback)

Clean all that up with Elements Proxy:

// One line of code regardless of the number of elements
const elements = elementsProxy();

if (x > y) {
  // Simple access to elements as properties
  elements.a.textConent = 'Hello world';
  // Cached lookups on subsequent access
  elements.a.hidden = false;
}

elements.b.classList.toggle('flex-col');
elements.c.addEventListener('click', callback)

Install

Don't bother! It's only a few lines of code, just copy-paste index.js into your app and be done.

Or import it:

import elementsProxy from 'https://unpkg.com/[email protected]';

Or install:

npm install elementsproxy

Requirements

This package has no dependencies and uses JavScript's Proxy object internally. Proxy has had full browser support for many years and should not require a polyfill. Compare your site's traffic to caniuse to see which browser versions would require a polyfill.