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

web-component-simple-program

v1.0.5

Published

A minimalist JS view library for Web Components inspired by Elm

Downloads

3

Readme

Web Component Simple Program

A minimalist JS view library for Web Components inspired by Elm

Install with npm or yarn.

npm i web-component-simple-program

Example:

import {
  Html,
  HtmlAttributes,
  HtmlEvents,
  render
} from "web-component-simple-program";

const { div, text, button } = Html;
const { class_ } = HtmlAttributes;
const { onclick } = HtmlEvents;

const dom = div()([
  span([class_("text-red")])([text("hello world")]),
  button([onclick(e => console.log(e))])([text("Click Me")])
]);

render(document, dom);

Use the updateNode helper to override the nodes attributes and children

import {
  Html,
  HtmlAttributes,
  HtmlEvents,
  updateNode,
  render
} from "web-component-simple-program";

const { div, text, button } = Html;
const { class_, id } = HtmlAttributes;
const { onclick } = HtmlEvents;

const buttonHandler = _ => {
  updateNode(document.getElementById("title"))([class_("text-green")])([
    text("goodbye world")
  ]);
};

const dom = div()([
  span([id("title"), class_("text-red")])([text("hello world")]),
  button([onclick(buttonHandler)])([text("Click Me")])
]);

render(document, dom);

If managing state, I recommend using Program (Inspired by The Elm Architecture)

import {
  Html,
  HtmlAttributes,
  Program,
  updateNode,
  main
} from "web-component-simple-program";

const { div, text, button } = Html;
const { class_, id } = HtmlAttributes;
const { main, toModel, toMsg, toUpdate, Events } = Program;

const UpdateTitle = "@@app/UPDATE_TITLE";

const init = ({ title }) => toModel({ title });

const update = msg => model => {
  switch (msg.payload) {
    case UpdateTitle:
      return toModel({ ...model, title: msg.payload.title });
    default:
      return toModel(model);
  }
};

// Instead of using a Virtual DOM,
// viewUpdate (which is passed into toUpdate as the second argument)
// is called after the update function
// which allows manual changes to be made to the DOM for now
const viewUpdate = root => [
  model =>
    updateNode(root.getElementById("title"))([class_("text-green")])([
      text(model.title)
    ]),
  model =>
    updateNode(root.getElementById("button"))()([
      text("Click Me" + model.title)
    ])
];

const view = root => model => {
  // Program Events intercept the HTMLEvents to handle async msg passing
  // these events now take in a function that returns a Msg
  // dispatch is also an added event if needed
  // Ex. dispatch(toMsg(UpdateTitle, {title: "blah"}))
  const { onclick } = Events(root);
  return div()([
    span([id("title"), class_("text-red")])([text(model.title)]),
    button([
      id("button"),
      onclick(e => toMsg(UpdateTitle, { title: "goodbye world" }))
    ])([text("Click Me")])
  ]);
};

class MyCustomElement extends HTMLElement {
  connectedCallback() {
    const props = {
      title: this.getAttribute("title") || ""
    };

    main(createRoot(this), {
      init: init(props),
      update: toUpdate(update, viewUpdate),
      view
    });
  }
}

customElements.define("my-custom-element", MyCustomElement);