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

velements

v1.0.3

Published

Minimalistic JSX elements that do not require React

Downloads

4

Readme

Virtual Elements

Use the power of JSX in your app without React!

Create elements using JSX:

/* @jsx h */

import h from 'velements'; // es6 
const {h} = require('velements'); // commonjs

const virtualElement = <div id='my-div'><p>text</p></div>;

Or in plain JavaScript:

const virtualElement = h('div', { id: 'my-div' }, h('p', null, 'text'));

Then use them like regular DOM elements:

document.getElementById('container').appendChild(virtualElement.toElement());

Boost your templates

Handlebars templates are very limiting in terms of logic you can do inside of them
and writing helpers for every peace of logic can be challenging and time consuming.

Why not just write plane javascript functions:

/* @jsx h */
const myPage = (title, text) =>
{
    return (
        <div>
            <h1>{title}</h1>
            <p>{text}</p>
        </div>
    );
};

const app = (loggedIn, title, text) =>
{
    return (
        <div>
            {header()}
            <br/>
            {loggedIn ? loginPage() : myPage(title, text)}
        </div>
    );
}

const virtualElement = app(/*...*/);

You can treat a virtual element like a regular string:

const str = virtualElement.toString();

const html = `<html><body>${virtualElement}</body></html>`;

This removes the need to compile templates and the resulting HTML is already minified.
This greatly improves server response time when doing Server Side Rendering.

React Compatible

Make your code usable by both Vanilla JavaScript apps as well as React apps.

When you want to switch to React world you simply convert your element:

const reactElement = virtualElement.toReactElement();

Or in your component:

const MyReactComponent = (props) =>
{
    return (
        <div>
            <MyOtherComponent/>
            {virtualElement.toReactElement()}
        </div>
    );
}

It can also be rendered by react-dom:

ReactDOM.render(
    virtualElement.toReactElement(),
    document.getElementById('container')
);

You can also inject React into the converter.
The default value is React = require('react')

const reactElement = virtualElement.toReactElement(React);