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

hyper-fun

v0.0.2

Published

Fun way to build app with hyperscript and observable

Downloads

5

Readme

hyper-fun

fun way to build app with hyperscript and observable

npm package browser build

live todoMVC sample

What's this

With hyperscript and observable as core + render/diffing, we get a decent view layer for building web app. No compiler is needed. If you itch for using html templating instead of hyperscript you can substitute with htm.

observable is using my fork version which has non-breaking updated features that have slightly modern interface + hyperscript with event caching.

Usage

has a new option setting called useHook. This's just synthetic sugar of the observable

import { o } from 'hyper-fun';

o.useHook(true)

const useState = o

// now observable has array like interface when declared
const [state, setState] = useState('foo')

// to make the observable behave like useReducer pass
// a second argument as initial value
const useReducer = o

const [state, dispatch] = useReducer(reducer, initialValue)

// to make it behave like an effect, call it with a function
// where it will pass the new value, whenever the value changes.
state(newState =>
    console.log('Was changed to', newState)
)

// to stop being notifed of these changes, call the function that was returned
const stop = state(newState =>
    console.log('Was changed to', newState)
)
// then some time later
stop()

A simple usage case

import { render, h, o as useState } from 'hyper-fun'

const [state, setState] = useState([])

const app = state =>
    h('div',
        h('button', {
            onclick: () => {
                state.push(state.length)
                if (state.length > 10) {
                    state = []
                }
                setState(state)
            }
        }, 'pop'),
        state.length ? 
            h('ul',
                state.map((s, i) => 
                    h(`li#${i}`, s)
                )
            ) : null
    )

render(document.getElementById('app'), state, app)

Samples

run npm run todo or npm run vdom to see working sample

Extra

has a new interface called fun. This basically an accessor for cleaner codes i.e which has advantage when you want want to loop/compute observable value directly.

import { o } from 'hyper-fun'

const { 
    fun 
} = o

// original inteface
onclick: e => {
    setState(state() + 1)
}
// instead with accessor
onclick: fun(s =>
   setState(s + 1)
, state)