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

domz

v1.0.0

Published

a proxy function to help build virtual DOM trees from functions

Downloads

24

Readme

domz

a proxy function to help build virtual DOM trees from functions

A proxy for react createElement (or h if using Preact, Hyperapp etc.) that allows you to describe interfaces much with JSX but just using regular JavaScript function calls instead. Views built like this require no transpilation and no prior knowledge of proprietary syntax. This is not a novel concept but the implementation is quite unique.

import domz from 'https://unpkg.com/domz'
const { div, h1, button, ul, li } = domz(React.createElement)  

ReactDOM.render(
  div([
    h1('Look Ma, optional props argument!'),
    button({ onclick: console.log }, 'Click Me'),
    ul([1,2,3].map(li)),
  ]),
  document.body
)

Features

  • No transpilation step or proprietary syntax
  • Exhaustive tag list and compatible with custom tags
  • Option props arguments for extra terse container elements
  • Designed to be generic and work with various frameworks
  • Extra small source that can be imported as an ES module

Usage

This library is intended to be framework agnostic. So before using the package you need to configure it to create virtual dom nodes in a shape the framework you are using expects to receive. You can then go ahead and destructure whatever DOM elements you need from it.

const { div, h1, button } = domz(React.createElement)  
const { div, h1, button } = domz(Preact.h)
const { div, h1, button } = domz(Hyperapp.h)

If you want to go totally rogue you could bind the configured domz instance to the window to make it globally available throughout your project.

window.domz = domz(React.createElement)

Implementation

The domz function generates the HTML tags upon request (and caches them in case they are requested again) using a JavaScript Proxy. This means that (unlike some solutions) the source code is very small and comprehendible. It might seem like magic at first but don't be dismayed, it is just JavaScript and it has great browser support.

(...args) => args[0] && typeof args[0] === "object" && !Array.isArray(args[0])
    ? h(name, ...args)
    : h(name, {}, ...args))

Essentially all the proxy does is forward the name and arguments (props?, children) of the original function invocation to another function that will call createElement or h appropriately.

Acknowledgement

This project took inspiration from a few other implementations namely: