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

weldkit

v0.1.11

Published

HTML elements library for web components

Downloads

12

Readme

Weldkit

Create web and desktop applications using web components.

Installation

cd myproject
npm install weldkit

Getting started

There are four base classes to create web components:

  • WebAppElement: Used to create web applications
  • ElectronAppElement: Used to create desktop applications
  • PageElement: Used to create page elements
  • ViewElement: Used to create view elements
  • FragmentElement: Used to create fragment elements

All these are modules exported by the weldkit module. These elements are meant to be used in a hierarchical way, so the App element should be at the at the root of the documents body.

body
|
+--> AppElement
      |
      +--> PageElement
            |
            +--> ViewElement
                 |
                 +--> FragmentElement

In this hierarchy view elements are optional, so a fragment element may be a child of a page element. A fragment element would be for example a table, a form, a list, in general, an HTML UI widget. A view is a collection of fragments that work together. The page element is used to hold an entire screen, so at any given time only one page is active and visible to the user, who may navigate between different screens to interact with the application.

To use a base element, simply import it and extend your class, like so:


// MyAppElement.js
import {WebAppElement} from 'npm_modules/weldkit/index.js';

class MyAppElement extends WebAppElement {
  
  constructor() {
    super();
  }
  
  
}

All base element classes extend from HTMLElement class, so they share the same API, which include HTML element lifecycle methods, such as (see MDN guide: Using custom elements):

  • connectedCallback
  • disconnectedCallback
  • adoptedCallback
  • attributeChangedCallback

Your element should be a module, so it has to be exported. But before you should register it like so:

customElements.define('my-app', MyAppElement);

To run your app, you need an HTML document that looks similar to this:

<!DOCTYPE html>
<html>
<head>
    <script src="/node_modules/systemjs/dist/system-production.js"></script>
    <script type="module" src="node_modules/weldkit/index.js"></script>
    <script type="module" src="MyAppElement.js"></script>
</head>
<body>
    <my-app data-role="app"></my-app>
</body>
</html>

weldkit relies on SystemJS to handle commonJS modules, so make sure to include the library first, like in the example above. Also note the role attribute, weldkit relies on such attributes to identify special components since the tag name is arbitrary and thus cannot be used to identify a component's role. Other roles are page, for page elements and view, for view elements.

Check out the web app example included in the project.

Currently weldkit is under heavy development, so it is unstable. Keep tuned to our twitter for updates.