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

@hydrophobefireman/qwc

v0.0.6

Published

quick and easy webcomponents without needing to write any javascript classes yourself

Downloads

15

Readme

QWC - Quick Web Components

QWC is the simplest way to create a new webcomponent, no need to write classes, QWC does that for you.

Usage

  1. Quick dirty non reactive element:

    index.html

    <template is="custom" custom-element="custom-element-name">
      <style>
        .your-scoped-css {
        }
      </style>
      <button>My Custom Element</button>
    </template>
    <custom-element-name></custom-element-name>

    App.js

    import { init } from "@hydrophobefireman/qwc";
    init();
  2. Custom logic for your element

    index.html

    <template is="custom" custom-element="my-custom-element">
      ...
    </template>
    <my-custom-element></my-custom-element>

    App.js

    import { init } from "@hydrophobefireman/qwc";
    init({
      "my-custom-element": {
        modifyConstructor(constructor) {
          // modify class constructor
        },
        observedAttributes: [
          {
            prop: "src",
            listener(oldVal, newVal) {
              //handle change
            }
          }
        ],
        modifyPrototype(prototype) {
          Object.defineProperty(prototype, "connectedCallback", {
            value() {
              //runs when element is connected (added to dom)
            }
          });
        }
      }
    });
  1. Dynamic properties in the dom

    index.html

    <template is="custom" custom-element="button-counter">
      <div data-text-content="currentDate"></div>
      <button
        updates-reactively
        data-text-content="count"
        data-onclick="handleClick"
      ></button>
    </template>
    <button-counter></button-counter>
    Note: only use attribute updates-reactively if your event listeners bring changes to your <custom-element/> otherwise using the attribute has no effect and leads to unnecessary updates.

    App.js

    import { init } from "@hydrophobefireman/qwc";
    const conf = {
      "button-counter": {
        count: 0,
        handleClick() {
          conf.count++;
        },
        currentDate: new Date().toString()
      }
    };
    init(null, conf);

NOTE: QWC prefers your <template> elements to be inlined in your html instead of having to write html-in-js. But you can provide it with all template elements if you prefer, as the 3rd argument

Installation

npm i @hydrophobefireman/qwc --save