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

nchantjs

v1.1.1

Published

A teeny html rendering library inspired by the elm language.

Downloads

10

Readme

nchantjs

A teeny library for building web apps. I was inspired by redux, elm, and functional reactive style programming. Its pretty vanilla, but it is intended to be used like elm, in a particular architecture that does not vary.

Docs

!!Work in progress!! https://arlenner.github.io/nchantjs/docs/index

How to use it:

  • make a root element to build off of
    <!DOCTYPE html>
    <!-- ...html stuffs><-->
    <body>
      <div id="root"></div>
    </body>
  • in your code, define a model
    const DEFAULT = { my: 'default', model: 'props' }
  • nchant uses action-like messages in the simplest possible way. You'll need to define them and then map them to corresponding update functions in an object:
    const Inc = '[Msg] Inc'
    const Say = '[Msg] Say'
    const UMap = {
        [Inc]: (model, n) => ({ ...model, value: model.value + n }),
        [Say]: (model, what, who) => ({...model, greeting: what +', ' + who})
    }
  • now build a store stream to push changes in your model to the DOM:
    const mystore = store(DEFAULT, Umap)
  • then use the variety of functions provided to build up your html (make sure you make your view functions take a model as a parameter):
    const myview = model => div([/*atts*/],[/*els*/])
  • finally hook it all together using the connect function:
    connect(mystore, myview)

Awesome! Now it should:

  • render the supplied component to the dom

  • react to changes in the dom, re-rendering only the changed portions

But now you want more. Separate files, multiple components - something non-trivial. Use the metaStore function and provide either a map or an array of key-value-pairs:

    //... index.js
    import * as fromA from './component-a'
    import * as fromB from './component-b'

    const rootStore = metaStore([
        [fromA.model, fromA.update],
        [fromB.model, fromB.update]
        //...
    ])
    const rootView = model => div(
        [],
        [fromA.view(model),
         fromB.view(model)
        ]
    )
    connect(rootStore, rootView)