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

globus

v0.1.3

Published

Functional reactive JavaScript front-end architecture

Downloads

16

Readme

Globus

Functional reactive JavaScript front-end architecture


Globus is an opinionated but loosely coupled reactive front-end architecture. It is a combination of the following:

Globus is not really well documented yet, but there is API documentation on the individual projects, and i am planning to make an example application.

Example app

import { createApp } from "globus";

const reducers = {
  counter: {
    // initial counter state
    initial: {value: 0},

    increment: (state, addend) =>
      state.set("value", state.get("value") + addend || 1)
  }
};

function View($, _) {
  return div(".hello",
    h1("Mandatory counter app"),
    button(
      {
        // Dispatch counter increment action on click
        $click: () => $.counter.increment(1)
      },
      // Show the current value of the counter
      "Value: " + _.counter.value)
  );
}

document.addEventListener("DOMContentLoaded", function() {
  createApp(reducers, View);
});

Suggested folder structure

my-application/
  reducers/
  views/
  actions/
  lib/
    transport/
    data/
    validation/

Larger applications may introduce an additional domain level:

my-application/
  core/
    reducers/
    views/
    actions/
    lib/
      transport/
      data/
  users/
    reducers/
    views/
    actions/
    lib/
      validation/
  • reducers is for describing state changes only. no other side effects.
  • actions contain functions that may invoke reducersm while doing other io, like calling backend actions etc
  • views contain view templates, and possibly helper functions
  • lib contains helper functions, as well as stuff like
  • lib/transport data adapters for server communtication, converters,
  • lib/data functions dealing with internal data formats, like resource representations, and
  • lib/validation validator functions