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

@browserkids/web-components

v0.8.0

Published

Non-transpiled ES13+ web components helper functions.

Downloads

7

Readme

@browserkids/web-components

npm version Known Vulnerabilities Build Status Dependency Status

This is a collection of useful web components helper functions. They are all written in latest/cutting edge ECMAScript 2022 code and are not transpiled.

Installation

Using a CDN

Fastest way to get going. See for yourself:

<script type="module">
import { define } from 'https://unpkg.com/@browserkids/web-components';

define(class MyElement extends HTMLElement {
  /* Your custom element logic. */
});
</script>

Using a bundler

Semi-fast way as well. Just install it via npm.

npm install -S @browserkids/web-components

Import the functions where you need them.

import { define } from '@browserkids/web-components';

Browser support

Almost every function uses at least one feature of ECMAScript 2022 , but no ESNext features — promised. So support should be fine for “evergreen” browsers at the time of writing. This means that Internet Explorer is out of the game.

As this library is not transpiled nor ever will be, you should use polyfills in case you need to support a specific browser version.

API

  1. define(elementConstructor)

    The define() helper function registers a custom element constructor to the CustomElementRegistry. To reduce redundant tasks like creating a ShadowDOM, binding attributes, setting up event listeners or fetching DOM references, the given element constructor will be extended and enhanced to have a consistent developing experience.

    <my-element></my-element>
       
    <script type="module">
      import { define } from 'https://unpkg.com/@browserkids/web-components';
       
      define(class MyElement extends HTMLElement {
      // By default define() uses the class name as element name, 
      // you can override this by defining a custom name.
      static name = 'my-element';
       
      // You can define a static settings field to override the settings 
      // for the individual functions that define() is using.
      static settings = {
        bindAttributes: {},
        bindEventListeners: {},
        createShadowRoot: {},
        findReferences: {},
      };
         
      // Will be used by bindAttributes and turns into a proxy object.
      data = {};
       
      // Will be used by createShadowRoot for shadow dom creation.
      template = '';
         
      // Will be called once the element has been inserted to the DOM,
      // and the constructor of that class has finished.
      ready() {}
    });
       
    </script>