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

hypersvg

v0.0.3

Published

SVG is very powerful when used inline, however using the DOM API is verbose. Even if you're using JSX or Hyperscript, there are a lot of properties and magic strings to remember.

Downloads

2

Readme

HyperSVG

SVG is very powerful when used inline, however using the DOM API is verbose. Even if you're using JSX or Hyperscript, there are a lot of properties and magic strings to remember.

This library provides a thin, library-agnostic helper API for rendering SVG elements - regular DOM elements or virtual DOM elements.

(Currently this is more of an idea or pattern than a library. It's also a place to collect SVG snippets I've found useful.)

The idea is that you provide a hyperscript-like render function with the following signature:

type HyperScript = (
    selector: string,
    attributes?: {[id: string]: any},
    ...children: any[]
) => any

For example: React's createElement or Mithril's m or Hyperscript's h function.

HyperSVG functions will return a rendered SVG structure (whatever your function outputs.)

Usage

Can be used two ways:

1. Plain functions

You can call the exported functions and provide the hyperscript function every time:

// Substitude Hyperscript for Mithril (m)
// or React (createElement) etc.
import h from 'hyperscript'
import {svg, triangle} from 'hypersvg'
svg(h,
    triangle(h, {
        angle: 90,
        className: 'green-triangle'
    })
)

This has the advantage of being easily tree-shaken. Or being bound or composed by your application.

2. API Instance

Otherwise you can create an instance of the API and inject the hyperscript function once on initialization, along with some default attribute values:

import h from 'hyperscript'
import HyperSVG from 'hypersvg'
const {svg, triangle} = HyperSVG(h, {
    width: '2em',
    height: '32px',
    viewBox: '0 0 32 32',
    className: 'my-svg'
})
// Then use it like this:
svg(
    triangle({
        angle: 90,
        className: 'green-triangle'
    })
)

The default attributes that you provide will be applied to every HyperSVG.svg call made from the returned API instance. Any defaults can be overridden in the attributes provided to any HyperSVG.svg call. If you do not provide any default attributes or when using HyperSVG.svg, the following values will be used:

{
    width: '1em',
    height: '1em',
    viewBox: '0 0 1 1'
}

Which makes them convenient for use inline with text content and as a 'normalized' size.

Keep in mind that it's also easy to create your own application-specific wrapper to inject the hyperscript dependency, set defaults or whatever else you find useful.