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

phomo

v0.1.1

Published

Another JavaScript framework for your FOMO.

Downloads

2

Readme

Phomo

Another JavaScript framework for your FOMO.

Warning: Do not use this library except for fun. It doesn't belong anywhere near a production environment. Seriously.

API

h

The h function allows us to create vDOM nodes.

const h = tag => (props = {}) => (...children) => ({
  tag,
  props,
  children,
  key: props.key
})

It can be used like so to make vDOM:

const view = actions => state => (
  h('div')({ class: state.className })(
    h('h1')()('Hello from Phomo'),
    h('p')()('A tiny UI library for funsies!')
  )
)

App

The app function generates our application and binds our actions in order to update the app.

It takes four arguments entry, view, actions and state.

An entry is the DOM node where we insert our application.

A view is a curried function that receives actions and state and returns the derived virtual DOM.

The actions object contains methods to update our application state with. These actions must follow a specific signature, like so:

const actions = {
  handleClick: value => state => ({ foo: state.foo + value })
  // return some partial state object to be merged into the app state
}

The state object is a plain JavaScript object used to supply values to our application. Thus, a view receives these two objects like so:

const state = {
  foo: true
}

const actions = {
  toggleFoo: () => state => ({ foo: !state.foo })
}

const view = actions => state => (
  h('div')()(
    h('p')()(`The value of foo is: ${state.foo}`),
    h('button')({ onclick: () => actions.toggleFoo() })('Toggle')
  )
)

Thus, app takes these arguments and an entry to generate our application, and re-renders the application with every action.