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 🙏

© 2025 – Pkg Stats / Ryan Hefner

midgard-core

v0.1.4

Published

Frontend core module providing common capabilities

Readme

midgard-core

Frontend core module written in pure JavaScript providing common capabilities. It is published as an npm package and used as a dependency in the framework specific wrappers (midgard-angular, midgard-react).

The purpose of this project is to provide a common core for all Midgard implementations. All capabilities developed in this project should be generic enough that they would not force any of the framework specific implementations on top of it to adopt patterns which are not natural for those respective frameworks.

Currently, midgard-core implements 4 major features: an HTTP Client, a Redux Store, an oAuth Client, and a Logging Library

HTTP Client

The HTTP Client exposes just one method which allows developers to make HTTP requests of all kinds. This method - request - in turn wraps the axios library.

Redux Store

Plain Redux store implemented by the redux npm package, with redux-observable on top to provide Observables support. The package exposes createStore, createSelector, combineReducers, combineEpics, ofType, createEpicMiddleware, applyMiddleware and compose. This offers felxibility to either adopt one or both packages in the framework specific implementations of Midgard.

oAuth Client

Simple oAuth client which currently only supports credential based authentication provided through authenticateWithCredentials

Logging Library

Exposes a Logger class which can be instantiated with a few options which configure behavior:

  • logToConsole - whether or not logged messages should be logged to the console as well
  • logToServer - whether or not logged messages should be logged to the server as well
  • APIURL - the server endpoint to send logged messages to. If this is not defined, logged messages will go to whatever endpoint was defined in environment variables for the deployment.

Logged messages can be categorized into various levels. Currently, those levels are LOG, TRACE, DEBUG, WARN, and ERROR. The logger will attempt to route messages to the correct console method, if it is available, based on the logLevel defined. Server side logging will also separate log messages based on these categories.