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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@netflix/x-element

v2.0.0

Published

A dead simple basis for custom elements.

Readme

  x-element
  _________
 / /__ __\ \
/ / \ \ / \ \
\ \ /_\_\ / /
 \_\_____/_/

A dead simple basis for custom elements. It provides the following functionality:

  • Efficient DOM generation and data binding using integrated templating engine
  • Automatic .property to [attribute] reflection (opt-in)
  • Automatic [attribute] to .property synchronization (one-directional, on connected)
  • Simple and efficient property observation and computation
  • Simple delegated event handling
  • Useful error messages

See SPEC.md for all the deets.

Installation:

Save a local copy to your project:

curl -O https://raw.githubusercontent.com/Netflix/x-element/main/x-element.js \
     -O https://raw.githubusercontent.com/Netflix/x-element/main/x-parser.js \
     -O https://raw.githubusercontent.com/Netflix/x-element/main/x-template.js

Then import it:

import XElement from '/path/to/x-element.js';

...or load it directly from the web:

import XElement from 'https://deno.land/x/element/x-element.js';

...or use an importmap:

<script type="importmap">
  {
    "imports": {
      "@netflix/x-element": "https://deno.land/x/element/x-element.js"
    }
  }
</script>

Then import it using a bare module specifier...

import XElement from '@netflix/x-element';

...or use a package manager:

npm install @netflix/x-element

Then import it using a bare module specifier...

import XElement from '@netflix/x-element';

Project Philosophy:

  1. No compilation step is necessary for adoption, just import x-element.js
  2. Implement a minimal set of generalized functionality
  3. Make as few design decisions as possible
  4. Presume adopters are browser experts already (stay out of their way)
  5. Follow web platform precedents whenever possible
  6. Remain compatible with any browser which fully supports custom elements
  7. Prioritize simple syntax and useful comments in the code itself
  8. Avoid making developers learn new proprietary stuff
  9. Zero dependencies

Development:

npm install && npm start

Then...

  • http://localhost:8080