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 🙏

© 2026 – Pkg Stats / Ryan Hefner

stem-core

v6.4.6

Published

Frontend and core-library framework

Readme

Stem JS

npm package

Stem is somewhere between a framework and a library. It offers a set of classes and functions for all the standard scenarios you can encounter in modern web app development, with design patterns designed to work together.

Installation

You can either just download the source from git or from the npm repository as the stem-core npm package:

npm install --save-dev stem-core

If you want to quickly set up a new demo app, you can try to use the create-stem-app npm package:

npm install -g create-stem-app
create-stem-app your_app_name

Using the library

The Stem code is designed to be used as ES6 modules. The code is meant to be included in the build path for whatever bundling tool you use (webpack, rollup).

Build requirements

The source bundle is build with rollup, which you can install with: npm install -g rollup. To call it, just run rollup -c in the root project folder.

Why release another Javascript framework?

The world is full of them. Most of them are mediocre though, and I wanted to show some effort into another direction. The architecture isn't optimized for cool one-liners, but for maintenance and flexibility, that keeps intentionally as much of the functionality in non-core code as possible.

Check out the docs at https://stemjs.org/docs/. This framework is being used for about a year at https://csacademy.com/, and it really works a lot better than any other solution out there.

This is the initial open-sourcing effort, it'll get more cleaned-up and documented in the next few weeks/months, with some concrete examples.

Recommended parts

There's a lot of functionality implemented in Stem. The closer to the core code you go, the better is gets and will probably be clean-up and more commented in the future. You can check out UIBase for the basics of the UI framework. It's an OOP based architecture that piggybacks on the jsx synthax (although you can use it with plain JS). I also included the base state classes that we use to store instances of DB-backed objects in the browser. It's a simple alternative to Redux/Flux if you will.

License

The Stem code is released explicitly under public domain (AKA The Unlicense, I just like public domain more than the term "Unlicense"). There are no ugly copyright headers you need to keep, and you can copy/paste the code without any attribution. It make it easier to bundle your code, so you know a minimized production js can strip all comments away. In case you need extra assurance, this software is also licensed under Creative Commons 0 (https://creativecommons.org/publicdomain/zero/1.0/), you can pick your preferred license.