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

html-widgets

v1.1.0

Published

Tiny UI framework, typescript friendly, for server rendered websites

Downloads

6

Readme

Tiny UI framework, typescript friendly, for server rendered websites.

Designed to be easy to use and learn. Thinked for anyone who wants a similar approach to other modern frameworks but can't use them for whatever reason.

Goal:

  • Watch the DOM and search [data-widget] elements
  • Lazy load the chunk (or just run a function) you define for it
  • Run a destroy function when the element in removed from the DOM

Table of contents


Quick overview

Install

yarn add html-widgets

Define the widget

<div data-widget="MyWidget">...</div>

Write the WidgetFunction

export default (context, plugins) => {
  console.log("MyWidget found in the DOM");

  () => {
    console.log("MyWidget removed from the DOM");
  };
};

Init the observer and register the widgets

import HtmlWidgets from "html-widgets";
import MyWidget from "./widgets/MyWidget";

new HtmlWidgets({
  widgets: { MyWidget },
});

Init options

{
  // root html element to watch, default [data-widgets-root]
  rootElement?: string;

  // log when a Widget is initiated or destroyed
  logs?: boolean;

  // object of imported WidgetFunctions, not lazy loaded
  widgets?: { [x: string] : WidgetFunction };

  // lazy load method, like:
  // async (widget) => await import(`~/${widget}`)
  lazyImport: (componentName: string) => Promise<WidgetFunction>

  // helper functions that have access to same context of a WidgetFunction
  // accessible as second argument of a WidgetFunction
  plugins: (context: WidgetContext<unknown>) => {
    [x: string]: (...args: any[]) => any;
  };
}

in order to use lazyImport remember to update your webpack config:

// lazyImport: async (widget) => await import(`~/${widget}`)

resolve: {
    extensions: [".ts", ".js"],
    alias: {
        "~": path.resolve(__dirname, "./path/to/widgets/folder/"),
    },
},

Context

First argument of a WidgetFunction, it contains:

  • $el | HTMLElement that called the function
  • name | the name found in [data-widget]
  • props | found and converted attributes when initiated
  • propEffect | a function that is called every time a specific attribute (only props) changes

props

<div
  data-widget="MyWidget"
  :some-string="lorem ipsum"
  :some-number="123"
  :some-object="{ 'foo': 'bar' }"
  :some-array="[1, 2, 3]"
></div>
export default ({ props }) => {
  console.log(typeof props["some-string"]); // String
  console.log(typeof props["some-number"]); // Number
  console.log(typeof props["some-object"]); // Object
  console.log(typeof props["some-array"]); // Array
};

propEffect()

export default ({ propEffect }) => {
  const [name, setName] = propEffect("name", () => {
    console.log(":name attribute just changed, new value:", name.current);
  });

  // name.current -> updated and converted attribute value
  // setName(v) -> update method, also working with $el.setAttribute(`:${name}`, v)
};

Plugins

It's possible to register custom functionalities for your widgets using the plugins option. Functions declared here are accessible through the second argument of your widget function and have access to the same context of a WidgetFunction

Very simple example:

new HtmlWidgets({
  // ...
  plugins: (context) => {
    qs: (target) => context.$el.querySelector(target);
  },
});
<div data-widget="MyWidget">
  <div class="js_child">foo</div>
</div>
export default (context, { qs }) => {
  const child = qs(".js_child");
  console.log(child.innerText); // foo
};

Use with Typescript

import HtmlWidgets, {
  WidgetFunction as BaseWidgetFunction, WidgetContext
} from "html-widgets";

const plugins = (context: WidgetContext<any>) => ({
  qs: <T extends HTMLElement>(name: string): T => {
    return context.$el.querySelector(name) as T;
  },
});

type WidgetFunction<T> = BaseWidgetFunction<T, ReturnType<typeof plugins>>;

interface Props {
  msg: string;
}

const MyWidget: WidgetFunction<Props> = (context, plugins) => {
    console.log(context, plugins);
}

new HtmlWidgets({
  widgets: { MyWidget }
  plugins,
});