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

virtual-webcomponent

v1.0.0

Published

Render a custom element to a virtual-dom widget

Downloads

5

Readme

virtual-webcomponent stability

npm version build status test coverage downloads js-standard-style

This is a very bad idea. Rendering custom elements on the server has proven to be either fragile, slow or clunky so they should be avoided. Don't use this. You have been warned. This has been open sourced for legacy purposes only.

Render a custom element to a virtual-dom widget.

Installation

$ npm install virtual-webcomponent

Usage

const toWidget = require('virtual-webcomponent')

module.exports = render

function render (h) {
  return h('section.main', [
    toWidget(createCustomElement())
  ])
}

function createCustomElement () {
  const proto = Object.create(window.HTMLElement.prototype)
  proto.createdCallback = function () {
    this.textContent = 'hello cruel world'
  }
  return proto
}

API

vdomWidget = toWidget(customElement)

Takes a custom element prototype and creates a virtual-dom widget. Contains the following mapping of events:

| custom-element | virtual-dom | |-----------------------------|-------------------------| | .createdCallback() | called once on creation | | .attachedCallback() | .init | | .detachedCallback() | .destroy | | .attributeChangedCallback() | .update |

Rant

react.js is the new jQuery. Everything for the web is starting to be created using this framework, and history has taught us that all frameworks eventually die.

Though most of the efforts around webcomponents have turned out to be not very good (e.g. shadow dom, html imports), custom elements are alright. Just like react custom elements have a concept of lifecycle, only it's not tied to a framework.

By leveraging custom element prototypes and their lifecycle hooks, virtual-dom widgets can be created that act as nodes on a tree. This reduces virtual-dom to glue only, and when something better comes around the components can be easily ported to a new framework. This approach brings a much needed reuse / upgrade path to the browser, allowing developers to break free from the endless rewriting and relearning whenever a new framework comes around.

See Also

License

MIT